diff --git a/aix_utmp/cpp_stl_11.html b/aix_utmp/cpp_stl_11.html
index 99e25373d..3237592e2 100644
--- a/aix_utmp/cpp_stl_11.html
+++ b/aix_utmp/cpp_stl_11.html
@@ -581,7 +581,7 @@ <h3>aix_utmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/cpp_stl_98.html b/aix_utmp/cpp_stl_98.html
index 888d3de03..12316f9c5 100644
--- a/aix_utmp/cpp_stl_98.html
+++ b/aix_utmp/cpp_stl_98.html
@@ -610,7 +610,7 @@ <h3>aix_utmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/csharp.html b/aix_utmp/csharp.html
index 284f3f6dc..c3b46be3a 100644
--- a/aix_utmp/csharp.html
+++ b/aix_utmp/csharp.html
@@ -468,7 +468,7 @@ <h3>AixUtmp.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/go.html b/aix_utmp/go.html
index 2230c6ab3..6666c256e 100644
--- a/aix_utmp/go.html
+++ b/aix_utmp/go.html
@@ -461,7 +461,7 @@ <h3>aix_utmp.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/graphviz.html b/aix_utmp/graphviz.html
index db0efc656..353b24181 100644
--- a/aix_utmp/graphviz.html
+++ b/aix_utmp/graphviz.html
@@ -291,7 +291,7 @@ <h3>aix_utmp.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/index.html b/aix_utmp/index.html
index b159e5539..0f112b17c 100644
--- a/aix_utmp/index.html
+++ b/aix_utmp/index.html
@@ -316,7 +316,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/java.html b/aix_utmp/java.html
index 1e5e26be1..e2a3e4083 100644
--- a/aix_utmp/java.html
+++ b/aix_utmp/java.html
@@ -496,7 +496,7 @@ <h3>AixUtmp.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/javascript.html b/aix_utmp/javascript.html
index 546d3b56c..42325cc3c 100644
--- a/aix_utmp/javascript.html
+++ b/aix_utmp/javascript.html
@@ -427,7 +427,7 @@ <h3>AixUtmp.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/lua.html b/aix_utmp/lua.html
index 5710c0b7a..7c4b7f77f 100644
--- a/aix_utmp/lua.html
+++ b/aix_utmp/lua.html
@@ -348,7 +348,7 @@ <h3>aix_utmp.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/nim.html b/aix_utmp/nim.html
index b51f05991..e1ad8ee34 100644
--- a/aix_utmp/nim.html
+++ b/aix_utmp/nim.html
@@ -399,7 +399,7 @@ <h3>aix_utmp.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/perl.html b/aix_utmp/perl.html
index e3840969c..baee096e0 100644
--- a/aix_utmp/perl.html
+++ b/aix_utmp/perl.html
@@ -448,7 +448,7 @@ <h3>AixUtmp.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/php.html b/aix_utmp/php.html
index 48899482d..850c86efa 100644
--- a/aix_utmp/php.html
+++ b/aix_utmp/php.html
@@ -390,7 +390,7 @@ <h3>AixUtmp.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/python.html b/aix_utmp/python.html
index 9fd4a7eec..cf2454dba 100644
--- a/aix_utmp/python.html
+++ b/aix_utmp/python.html
@@ -363,7 +363,7 @@ <h3>aix_utmp.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/aix_utmp/ruby.html b/aix_utmp/ruby.html
index fed23dd44..67b2c556c 100644
--- a/aix_utmp/ruby.html
+++ b/aix_utmp/ruby.html
@@ -407,7 +407,7 @@ <h3>aix_utmp.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/cpp_stl_11.html b/allegro_dat/cpp_stl_11.html
index e2377451b..ae0c4b813 100644
--- a/allegro_dat/cpp_stl_11.html
+++ b/allegro_dat/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -1144,7 +1144,7 @@ <h3>allegro_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/cpp_stl_98.html b/allegro_dat/cpp_stl_98.html
index 70551bc78..bd3b9a0e9 100644
--- a/allegro_dat/cpp_stl_98.html
+++ b/allegro_dat/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -1251,7 +1251,7 @@ <h3>allegro_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/csharp.html b/allegro_dat/csharp.html
index c26a60606..20b2ff727 100644
--- a/allegro_dat/csharp.html
+++ b/allegro_dat/csharp.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -825,7 +825,7 @@ <h3>AllegroDat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/go.html b/allegro_dat/go.html
index bca3af95a..3195e4b2c 100644
--- a/allegro_dat/go.html
+++ b/allegro_dat/go.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -883,7 +883,7 @@ <h3>allegro_dat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/graphviz.html b/allegro_dat/graphviz.html
index 422a033df..07ae1184a 100644
--- a/allegro_dat/graphviz.html
+++ b/allegro_dat/graphviz.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -468,7 +468,7 @@ <h3>allegro_dat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/index.html b/allegro_dat/index.html
index cc0b49504..780f93ea3 100644
--- a/allegro_dat/index.html
+++ b/allegro_dat/index.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -445,7 +445,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/java.html b/allegro_dat/java.html
index 07ab78676..6699820bb 100644
--- a/allegro_dat/java.html
+++ b/allegro_dat/java.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -875,7 +875,7 @@ <h3>AllegroDat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/javascript.html b/allegro_dat/javascript.html
index 2bc4aee42..1161378ba 100644
--- a/allegro_dat/javascript.html
+++ b/allegro_dat/javascript.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -651,7 +651,7 @@ <h3>AllegroDat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/lua.html b/allegro_dat/lua.html
index a8af8728b..f62cf9068 100644
--- a/allegro_dat/lua.html
+++ b/allegro_dat/lua.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -583,7 +583,7 @@ <h3>allegro_dat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/nim.html b/allegro_dat/nim.html
index 961617897..a6b4f8037 100644
--- a/allegro_dat/nim.html
+++ b/allegro_dat/nim.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -677,7 +677,7 @@ <h3>allegro_dat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/perl.html b/allegro_dat/perl.html
index daf15fd97..c61a28677 100644
--- a/allegro_dat/perl.html
+++ b/allegro_dat/perl.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -934,7 +934,7 @@ <h3>AllegroDat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/php.html b/allegro_dat/php.html
index 2865c91fc..e9f3ac6e1 100644
--- a/allegro_dat/php.html
+++ b/allegro_dat/php.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -652,7 +652,7 @@ <h3>AllegroDat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/python.html b/allegro_dat/python.html
index 5b83f7676..06fa525a1 100644
--- a/allegro_dat/python.html
+++ b/allegro_dat/python.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -581,7 +581,7 @@ <h3>allegro_dat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/allegro_dat/ruby.html b/allegro_dat/ruby.html
index a474fde55..34067f542 100644
--- a/allegro_dat/ruby.html
+++ b/allegro_dat/ruby.html
@@ -105,14 +105,14 @@ <h1>Allegro data file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Allegro library for C (mostly used for game and multimedia apps
+                <p><p>Allegro library for C (mostly used for game and multimedia apps<br />
 programming) used its own container file format.</p>
-<p>In general, it allows storage of arbitrary binary data blocks
-bundled together with some simple key-value style metadata
-(&quot;properties&quot;) for every block. Allegro also pre-defines some simple
-formats for bitmaps, fonts, MIDI music, sound samples and
+<p>In general, it allows storage of arbitrary binary data blocks<br />
+bundled together with some simple key-value style metadata<br />
+(&quot;properties&quot;) for every block. Allegro also pre-defines some simple<br />
+formats for bitmaps, fonts, MIDI music, sound samples and<br />
 palettes. Allegro library v4.0+ also support LZSS compression.</p>
-<p>This spec applies to Allegro data files for library versions 2.2 up
+<p>This spec applies to Allegro data files for library versions 2.2 up<br />
 to 4.4.</p>
 </p>
             </div>
@@ -619,7 +619,7 @@ <h3>allegro_dat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/cpp_stl_11.html b/amlogic_emmc_partitions/cpp_stl_11.html
index 1dce48950..25576534d 100644
--- a/amlogic_emmc_partitions/cpp_stl_11.html
+++ b/amlogic_emmc_partitions/cpp_stl_11.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -582,7 +582,7 @@ <h3>amlogic_emmc_partitions.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/cpp_stl_98.html b/amlogic_emmc_partitions/cpp_stl_98.html
index 2e4fc9dcc..98be2476f 100644
--- a/amlogic_emmc_partitions/cpp_stl_98.html
+++ b/amlogic_emmc_partitions/cpp_stl_98.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -614,7 +614,7 @@ <h3>amlogic_emmc_partitions.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/csharp.html b/amlogic_emmc_partitions/csharp.html
index d7e7da86d..5ae115e62 100644
--- a/amlogic_emmc_partitions/csharp.html
+++ b/amlogic_emmc_partitions/csharp.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -469,7 +469,7 @@ <h3>AmlogicEmmcPartitions.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/go.html b/amlogic_emmc_partitions/go.html
index e65adda6f..1b601daaf 100644
--- a/amlogic_emmc_partitions/go.html
+++ b/amlogic_emmc_partitions/go.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -450,7 +450,7 @@ <h3>amlogic_emmc_partitions.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/graphviz.html b/amlogic_emmc_partitions/graphviz.html
index 453e03ce6..8676c02c5 100644
--- a/amlogic_emmc_partitions/graphviz.html
+++ b/amlogic_emmc_partitions/graphviz.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -304,7 +304,7 @@ <h3>amlogic_emmc_partitions.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/index.html b/amlogic_emmc_partitions/index.html
index 43f75dbea..7692292a4 100644
--- a/amlogic_emmc_partitions/index.html
+++ b/amlogic_emmc_partitions/index.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -328,7 +328,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/java.html b/amlogic_emmc_partitions/java.html
index c85da2b69..d4ee4ced2 100644
--- a/amlogic_emmc_partitions/java.html
+++ b/amlogic_emmc_partitions/java.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -481,7 +481,7 @@ <h3>AmlogicEmmcPartitions.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/javascript.html b/amlogic_emmc_partitions/javascript.html
index 4ad375354..0debe6bf1 100644
--- a/amlogic_emmc_partitions/javascript.html
+++ b/amlogic_emmc_partitions/javascript.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -414,7 +414,7 @@ <h3>AmlogicEmmcPartitions.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/lua.html b/amlogic_emmc_partitions/lua.html
index 5d4382e08..5ad560d7d 100644
--- a/amlogic_emmc_partitions/lua.html
+++ b/amlogic_emmc_partitions/lua.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -355,7 +355,7 @@ <h3>amlogic_emmc_partitions.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/nim.html b/amlogic_emmc_partitions/nim.html
index 4489726ef..7b3a0f3a5 100644
--- a/amlogic_emmc_partitions/nim.html
+++ b/amlogic_emmc_partitions/nim.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -386,7 +386,7 @@ <h3>amlogic_emmc_partitions.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/perl.html b/amlogic_emmc_partitions/perl.html
index 90d54bc0b..77338b7fc 100644
--- a/amlogic_emmc_partitions/perl.html
+++ b/amlogic_emmc_partitions/perl.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -452,7 +452,7 @@ <h3>AmlogicEmmcPartitions.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/php.html b/amlogic_emmc_partitions/php.html
index 7df2c5d3e..24d748773 100644
--- a/amlogic_emmc_partitions/php.html
+++ b/amlogic_emmc_partitions/php.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -380,7 +380,7 @@ <h3>AmlogicEmmcPartitions.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/python.html b/amlogic_emmc_partitions/python.html
index b13edeaf7..3f98b014e 100644
--- a/amlogic_emmc_partitions/python.html
+++ b/amlogic_emmc_partitions/python.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -386,7 +386,7 @@ <h3>amlogic_emmc_partitions.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/amlogic_emmc_partitions/ruby.html b/amlogic_emmc_partitions/ruby.html
index 6de293334..144c0f10e 100644
--- a/amlogic_emmc_partitions/ruby.html
+++ b/amlogic_emmc_partitions/ruby.html
@@ -105,15 +105,15 @@ <h1>Amlogic proprietary eMMC partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is an unnamed and undocumented partition table format implemented by
-the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson
-series at least, and probably others). They appear to use this rather than GPT,
-the industry standard, because their BootROM loads and executes the next stage
-loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT
-header would have to start. So instead of changing their BootROM, Amlogic
-devised this partition table, which lives at an offset of 36MiB (0x240_0000)
-on the eMMC and so doesn't conflict. This parser expects as input just the
-partition table from that offset. The maximum number of partitions in a table
+                <p><p>This is an unnamed and undocumented partition table format implemented by<br />
+the bootloader and kernel that Amlogic provides for their Linux SoCs (Meson<br />
+series at least, and probably others). They appear to use this rather than GPT,<br />
+the industry standard, because their BootROM loads and executes the next stage<br />
+loader from offset 512 (0x200) on the eMMC, which is exactly where the GPT<br />
+header would have to start. So instead of changing their BootROM, Amlogic<br />
+devised this partition table, which lives at an offset of 36MiB (0x240_0000)<br />
+on the eMMC and so doesn't conflict. This parser expects as input just the<br />
+partition table from that offset. The maximum number of partitions in a table<br />
 is 32, which corresponds to a maximum table size of 1304 bytes (0x518).</p>
 </p>
             </div>
@@ -406,7 +406,7 @@ <h3>amlogic_emmc_partitions.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/cpp_stl_11.html b/andes_firmware/cpp_stl_11.html
index 403de5224..32b88d6ee 100644
--- a/andes_firmware/cpp_stl_11.html
+++ b/andes_firmware/cpp_stl_11.html
@@ -478,7 +478,7 @@ <h3>andes_firmware.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/cpp_stl_98.html b/andes_firmware/cpp_stl_98.html
index 3ceb22252..e3c7f35b6 100644
--- a/andes_firmware/cpp_stl_98.html
+++ b/andes_firmware/cpp_stl_98.html
@@ -498,7 +498,7 @@ <h3>andes_firmware.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/csharp.html b/andes_firmware/csharp.html
index 9151fb164..33469c2bf 100644
--- a/andes_firmware/csharp.html
+++ b/andes_firmware/csharp.html
@@ -379,7 +379,7 @@ <h3>AndesFirmware.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/go.html b/andes_firmware/go.html
index 9e191bed9..7cbeb934d 100644
--- a/andes_firmware/go.html
+++ b/andes_firmware/go.html
@@ -364,7 +364,7 @@ <h3>andes_firmware.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/graphviz.html b/andes_firmware/graphviz.html
index 9282c8b60..007985ee8 100644
--- a/andes_firmware/graphviz.html
+++ b/andes_firmware/graphviz.html
@@ -285,7 +285,7 @@ <h3>andes_firmware.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/index.html b/andes_firmware/index.html
index 39e8fec0e..bef5219d8 100644
--- a/andes_firmware/index.html
+++ b/andes_firmware/index.html
@@ -272,7 +272,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/java.html b/andes_firmware/java.html
index 6ea3045a0..00d9b38ff 100644
--- a/andes_firmware/java.html
+++ b/andes_firmware/java.html
@@ -392,7 +392,7 @@ <h3>AndesFirmware.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/javascript.html b/andes_firmware/javascript.html
index 3eb49e439..8abc08c2b 100644
--- a/andes_firmware/javascript.html
+++ b/andes_firmware/javascript.html
@@ -347,7 +347,7 @@ <h3>AndesFirmware.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/lua.html b/andes_firmware/lua.html
index d6f68cb99..f38a6bfc0 100644
--- a/andes_firmware/lua.html
+++ b/andes_firmware/lua.html
@@ -299,7 +299,7 @@ <h3>andes_firmware.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/nim.html b/andes_firmware/nim.html
index 71ed3c09e..69f25f2e6 100644
--- a/andes_firmware/nim.html
+++ b/andes_firmware/nim.html
@@ -324,7 +324,7 @@ <h3>andes_firmware.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/perl.html b/andes_firmware/perl.html
index 339b27205..75e25e632 100644
--- a/andes_firmware/perl.html
+++ b/andes_firmware/perl.html
@@ -386,7 +386,7 @@ <h3>AndesFirmware.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/php.html b/andes_firmware/php.html
index 3e0d56758..c07c092b0 100644
--- a/andes_firmware/php.html
+++ b/andes_firmware/php.html
@@ -314,7 +314,7 @@ <h3>AndesFirmware.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/python.html b/andes_firmware/python.html
index 4aea879e9..3fb3790bf 100644
--- a/andes_firmware/python.html
+++ b/andes_firmware/python.html
@@ -335,7 +335,7 @@ <h3>andes_firmware.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/andes_firmware/ruby.html b/andes_firmware/ruby.html
index 84e933e88..0c7532192 100644
--- a/andes_firmware/ruby.html
+++ b/andes_firmware/ruby.html
@@ -347,7 +347,7 @@ <h3>andes_firmware.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/cpp_stl_11.html b/android_bootldr_asus/cpp_stl_11.html
index 24a37b4e9..1bce90b62 100644
--- a/android_bootldr_asus/cpp_stl_11.html
+++ b/android_bootldr_asus/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -527,7 +527,7 @@ <h3>android_bootldr_asus.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/cpp_stl_98.html b/android_bootldr_asus/cpp_stl_98.html
index b4f238450..dededf5ca 100644
--- a/android_bootldr_asus/cpp_stl_98.html
+++ b/android_bootldr_asus/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -547,7 +547,7 @@ <h3>android_bootldr_asus.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/csharp.html b/android_bootldr_asus/csharp.html
index c2a8848b2..24bfcdcfc 100644
--- a/android_bootldr_asus/csharp.html
+++ b/android_bootldr_asus/csharp.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -433,7 +433,7 @@ <h3>AndroidBootldrAsus.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/go.html b/android_bootldr_asus/go.html
index 8f94d073e..0990eb6b0 100644
--- a/android_bootldr_asus/go.html
+++ b/android_bootldr_asus/go.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -429,7 +429,7 @@ <h3>android_bootldr_asus.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/graphviz.html b/android_bootldr_asus/graphviz.html
index e2d712b0f..a7f84afd4 100644
--- a/android_bootldr_asus/graphviz.html
+++ b/android_bootldr_asus/graphviz.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -293,7 +293,7 @@ <h3>android_bootldr_asus.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/index.html b/android_bootldr_asus/index.html
index e3f1ec6c5..bb9746158 100644
--- a/android_bootldr_asus/index.html
+++ b/android_bootldr_asus/index.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -308,7 +308,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/java.html b/android_bootldr_asus/java.html
index ea7a1de2b..5e840334a 100644
--- a/android_bootldr_asus/java.html
+++ b/android_bootldr_asus/java.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -434,7 +434,7 @@ <h3>AndroidBootldrAsus.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/javascript.html b/android_bootldr_asus/javascript.html
index 289bb3b6e..339010b37 100644
--- a/android_bootldr_asus/javascript.html
+++ b/android_bootldr_asus/javascript.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -382,7 +382,7 @@ <h3>AndroidBootldrAsus.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/lua.html b/android_bootldr_asus/lua.html
index 442dd788b..aaa1245c2 100644
--- a/android_bootldr_asus/lua.html
+++ b/android_bootldr_asus/lua.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -333,7 +333,7 @@ <h3>android_bootldr_asus.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/php.html b/android_bootldr_asus/php.html
index 201a73630..9d14393b4 100644
--- a/android_bootldr_asus/php.html
+++ b/android_bootldr_asus/php.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -351,7 +351,7 @@ <h3>AndroidBootldrAsus.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/python.html b/android_bootldr_asus/python.html
index 1185d1780..be4b74e9d 100644
--- a/android_bootldr_asus/python.html
+++ b/android_bootldr_asus/python.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -364,7 +364,7 @@ <h3>android_bootldr_asus.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_asus/ruby.html b/android_bootldr_asus/ruby.html
index 5bb690762..de0f85379 100644
--- a/android_bootldr_asus/ruby.html
+++ b/android_bootldr_asus/ruby.html
@@ -105,10 +105,10 @@ <h1>ASUS Fugu bootloader.img format (version 2 and later):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader image which only seems to have been used on a few ASUS
-devices. The encoding is ASCII, because the <code>releasetools.py</code> script
+                <p><p>A bootloader image which only seems to have been used on a few ASUS<br />
+devices. The encoding is ASCII, because the <code>releasetools.py</code> script<br />
 is written using Python 2, where the default encoding is ASCII.</p>
-<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,
+<p>A test file can be found in the firmware files for the &quot;fugu&quot; device,<br />
 which can be downloaded from <a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a></p>
 </p>
             </div>
@@ -372,7 +372,7 @@ <h3>android_bootldr_asus.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/cpp_stl_11.html b/android_bootldr_huawei/cpp_stl_11.html
index b555196a9..bf8ffb916 100644
--- a/android_bootldr_huawei/cpp_stl_11.html
+++ b/android_bootldr_huawei/cpp_stl_11.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>android_bootldr_huawei.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/cpp_stl_98.html b/android_bootldr_huawei/cpp_stl_98.html
index ca22717f1..99a73c2b6 100644
--- a/android_bootldr_huawei/cpp_stl_98.html
+++ b/android_bootldr_huawei/cpp_stl_98.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -767,7 +767,7 @@ <h3>android_bootldr_huawei.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/csharp.html b/android_bootldr_huawei/csharp.html
index 04f402de9..462ab16c0 100644
--- a/android_bootldr_huawei/csharp.html
+++ b/android_bootldr_huawei/csharp.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -552,7 +552,7 @@ <h3>AndroidBootldrHuawei.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/go.html b/android_bootldr_huawei/go.html
index b9d0dfca4..c510f9d42 100644
--- a/android_bootldr_huawei/go.html
+++ b/android_bootldr_huawei/go.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -551,7 +551,7 @@ <h3>android_bootldr_huawei.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/index.html b/android_bootldr_huawei/index.html
index 5bec53e1e..18eac55d5 100644
--- a/android_bootldr_huawei/index.html
+++ b/android_bootldr_huawei/index.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -345,7 +345,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/java.html b/android_bootldr_huawei/java.html
index b558d84c7..5824a83e7 100644
--- a/android_bootldr_huawei/java.html
+++ b/android_bootldr_huawei/java.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -562,7 +562,7 @@ <h3>AndroidBootldrHuawei.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/javascript.html b/android_bootldr_huawei/javascript.html
index 01eb913f5..76cf10ee1 100644
--- a/android_bootldr_huawei/javascript.html
+++ b/android_bootldr_huawei/javascript.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -468,7 +468,7 @@ <h3>AndroidBootldrHuawei.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/lua.html b/android_bootldr_huawei/lua.html
index 42e93abb2..bc3585db2 100644
--- a/android_bootldr_huawei/lua.html
+++ b/android_bootldr_huawei/lua.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -416,7 +416,7 @@ <h3>android_bootldr_huawei.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/nim.html b/android_bootldr_huawei/nim.html
index 48733dde5..a5e8bbb54 100644
--- a/android_bootldr_huawei/nim.html
+++ b/android_bootldr_huawei/nim.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h3>android_bootldr_huawei.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/perl.html b/android_bootldr_huawei/perl.html
index e9972d74e..00c275ad8 100644
--- a/android_bootldr_huawei/perl.html
+++ b/android_bootldr_huawei/perl.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -541,7 +541,7 @@ <h3>AndroidBootldrHuawei.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/php.html b/android_bootldr_huawei/php.html
index 3bc303a32..31a6c8956 100644
--- a/android_bootldr_huawei/php.html
+++ b/android_bootldr_huawei/php.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -430,7 +430,7 @@ <h3>AndroidBootldrHuawei.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/python.html b/android_bootldr_huawei/python.html
index 53af80908..76c4dd716 100644
--- a/android_bootldr_huawei/python.html
+++ b/android_bootldr_huawei/python.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -435,7 +435,7 @@ <h3>android_bootldr_huawei.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_huawei/ruby.html b/android_bootldr_huawei/ruby.html
index 69202c9df..1845a0d6f 100644
--- a/android_bootldr_huawei/ruby.html
+++ b/android_bootldr_huawei/ruby.html
@@ -107,15 +107,15 @@ <h1>Huawei Bootloader packed image format:
             <div class="col-md-8">
                 <p><p>Format of <code>bootloader-*.img</code> files found in factory images of certain Android devices from Huawei:</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a></li>
 </ul>
-<p>All image versions can be found in factory images at
-<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To
-avoid having to download an entire ZIP archive when you only need one file
-from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and
-use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line
-tool</a> to list
+<p>All image versions can be found in factory images at<br />
+<a href="https://developers.google.com/android/images">https://developers.google.com/android/images</a> for the specific device. To<br />
+avoid having to download an entire ZIP archive when you only need one file<br />
+from it, install <a href="https://github.com/gtsystem/python-remotezip">remotezip</a> and<br />
+use its <a href="https://github.com/gtsystem/python-remotezip#command-line-tool">command line<br />
+tool</a> to list<br />
 members in the archive and then to download only the file you want.</p>
 </p>
             </div>
@@ -450,7 +450,7 @@ <h3>android_bootldr_huawei.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/cpp_stl_11.html b/android_bootldr_qcom/cpp_stl_11.html
index 464cc29a8..13ee5035c 100644
--- a/android_bootldr_qcom/cpp_stl_11.html
+++ b/android_bootldr_qcom/cpp_stl_11.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -795,7 +795,7 @@ <h3>android_bootldr_qcom.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/cpp_stl_98.html b/android_bootldr_qcom/cpp_stl_98.html
index 505fbb867..3d4b174b1 100644
--- a/android_bootldr_qcom/cpp_stl_98.html
+++ b/android_bootldr_qcom/cpp_stl_98.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -827,7 +827,7 @@ <h3>android_bootldr_qcom.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/csharp.html b/android_bootldr_qcom/csharp.html
index b5cdb934e..1ac35f23d 100644
--- a/android_bootldr_qcom/csharp.html
+++ b/android_bootldr_qcom/csharp.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -670,7 +670,7 @@ <h3>AndroidBootldrQcom.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/go.html b/android_bootldr_qcom/go.html
index 8158cfeda..f8b99c644 100644
--- a/android_bootldr_qcom/go.html
+++ b/android_bootldr_qcom/go.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -636,7 +636,7 @@ <h3>android_bootldr_qcom.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/graphviz.html b/android_bootldr_qcom/graphviz.html
index da92c7527..f30986c42 100644
--- a/android_bootldr_qcom/graphviz.html
+++ b/android_bootldr_qcom/graphviz.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -396,7 +396,7 @@ <h3>android_bootldr_qcom.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/index.html b/android_bootldr_qcom/index.html
index c7b69b7ed..f11af1e54 100644
--- a/android_bootldr_qcom/index.html
+++ b/android_bootldr_qcom/index.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -510,7 +510,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/java.html b/android_bootldr_qcom/java.html
index ae9852d1d..ccc59f37f 100644
--- a/android_bootldr_qcom/java.html
+++ b/android_bootldr_qcom/java.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -673,7 +673,7 @@ <h3>AndroidBootldrQcom.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/javascript.html b/android_bootldr_qcom/javascript.html
index 165431616..1cc0221db 100644
--- a/android_bootldr_qcom/javascript.html
+++ b/android_bootldr_qcom/javascript.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -621,7 +621,7 @@ <h3>AndroidBootldrQcom.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/lua.html b/android_bootldr_qcom/lua.html
index 576c2cb40..12d9d7c49 100644
--- a/android_bootldr_qcom/lua.html
+++ b/android_bootldr_qcom/lua.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -554,7 +554,7 @@ <h3>android_bootldr_qcom.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/nim.html b/android_bootldr_qcom/nim.html
index c5d625394..5bceb76c1 100644
--- a/android_bootldr_qcom/nim.html
+++ b/android_bootldr_qcom/nim.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -579,7 +579,7 @@ <h3>android_bootldr_qcom.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/perl.html b/android_bootldr_qcom/perl.html
index 6b43390e8..10c74b6bd 100644
--- a/android_bootldr_qcom/perl.html
+++ b/android_bootldr_qcom/perl.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -524,7 +524,7 @@ <h3>AndroidBootldrQcom.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/php.html b/android_bootldr_qcom/php.html
index b4925cc1f..d845c13fd 100644
--- a/android_bootldr_qcom/php.html
+++ b/android_bootldr_qcom/php.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -564,7 +564,7 @@ <h3>AndroidBootldrQcom.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/python.html b/android_bootldr_qcom/python.html
index 11c0461e1..d7b5f0612 100644
--- a/android_bootldr_qcom/python.html
+++ b/android_bootldr_qcom/python.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -585,7 +585,7 @@ <h3>android_bootldr_qcom.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_bootldr_qcom/ruby.html b/android_bootldr_qcom/ruby.html
index 23aa28e83..255d8e074 100644
--- a/android_bootldr_qcom/ruby.html
+++ b/android_bootldr_qcom/ruby.html
@@ -105,49 +105,49 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A bootloader for Android used on various devices powered by Qualcomm
+                <p><p>A bootloader for Android used on various devices powered by Qualcomm<br />
 Snapdragon chips:</p>
 <p><a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors">https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors</a></p>
-<p>Although not all of the Snapdragon based Android devices use this particular
-bootloader format, it is known that devices with the following chips have used
+<p>Although not all of the Snapdragon based Android devices use this particular<br />
+bootloader format, it is known that devices with the following chips have used<br />
 it (example devices are given for each chip):</p>
 <ul>
 <li>
 <p>APQ8064 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_S4_Pro">devices</a>)</p>
 <ul>
-<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),
+<li>Nexus 4 &quot;mako&quot;: <a href="https://androidfilehost.com/?fid=96039337900113996" title="bootloader-mako-makoz30f.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-mako&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/mako/+/33f0114/releasetools.py#98">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8974AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),
+<li>Nexus 5 &quot;hammerhead&quot;: <a href="https://androidfilehost.com/?fid=385035244224410247" title="bootloader-hammerhead-hhz20h.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-hammerhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/hammerhead/+/7618a7d/releasetools.py#116">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8992 (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),
+<li>Nexus 5X &quot;bullhead&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870177" title="bootloader-bullhead-bhz32c.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-bullhead&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/lge/bullhead/+/2994b6b/releasetools.py#126">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>APQ8064-1AA (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_600_(2013)">devices</a>)</p>
 <ul>
-<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Mobile) &quot;deb&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23501681358552487" title="bootloader-deb-flo-04.02.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-deb-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/deb/+/14c1638/releasetools.py#105">releasetools.py</a></li>
-<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),
+<li>Nexus 7 [2013] (Wi-Fi) &quot;flo&quot; <!-- raw HTML omitted -->(**)<!-- raw HTML omitted -->: <a href="https://androidfilehost.com/?fid=23991606952593542" title="bootloader-flo-flo-04.05.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-flo-flo&amp;type=files">other samples</a>),<br />
 <a href="https://android.googlesource.com/device/asus/flo/+/9d9fee9/releasetools.py#130">releasetools.py</a></li>
 </ul>
 </li>
 <li>
 <p>MSM8996 Pro-AB (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_820_and_821_(2016)">devices</a>)</p>
 <ul>
-<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel &quot;sailfish&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907154" title="bootloader-sailfish-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-sailfish&amp;type=files">other samples</a>)</li>
-<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:
+<li>Pixel XL &quot;marlin&quot; <!-- raw HTML omitted -->(*)<!-- raw HTML omitted -->:<br />
 <a href="https://androidfilehost.com/?fid=6006931924117907131" title="bootloader-marlin-8996-012001-1904111134.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-marlin&amp;type=files">other samples</a>)</li>
 </ul>
 </li>
@@ -159,11 +159,11 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 </ul>
 </li>
 </ul>
-<p><!-- raw HTML omitted -->(*)
-<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).
+<p><!-- raw HTML omitted -->(*)<br />
+<code>bootloader_size</code> is equal to the size of the whole file (not just <code>img_bodies</code> as usual).<br />
 <!-- raw HTML omitted --></p>
-<p><!-- raw HTML omitted -->(**)
-There are some data after the end of <code>img_bodies</code>.
+<p><!-- raw HTML omitted -->(**)<br />
+There are some data after the end of <code>img_bodies</code>.<br />
 <!-- raw HTML omitted --></p>
 <hr />
 <p>On the other hand, devices with these chips <strong>do not</strong> use this format:</p>
@@ -171,29 +171,29 @@ <h1>Qualcomm Snapdragon (MSM) bootloader.img format:
 <li>
 <p><!-- raw HTML omitted -->APQ8084<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_800,_801_and_805_(2013/14)">devices</a>)</p>
 <ul>
-<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -
+<li>Nexus 6 &quot;shamu&quot;: <a href="https://androidfilehost.com/?fid=745849072291678307" title="bootloader-shamu-moto-apq8084-72.04.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-shamu&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/moto/shamu/+/df9354d/releasetools.py#12">releasetools.py</a> -<br />
 uses &quot;Motoboot packed image format&quot; instead</li>
 </ul>
 </li>
 <li>
 <p><!-- raw HTML omitted -->MSM8994<!-- raw HTML omitted --> (<a href="https://en.wikipedia.org/wiki/Devices_using_Qualcomm_Snapdragon_processors#Snapdragon_808_and_810_(2015)">devices</a>)</p>
 <ul>
-<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),
-<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -
+<li>Nexus 6P &quot;angler&quot;: <a href="https://androidfilehost.com/?fid=11410963190603870158" title="bootloader-angler-angler-03.84.img">sample</a> (<a href="https://androidfilehost.com/?w=search&amp;s=bootloader-angler&amp;type=files">other samples</a>),<br />
+<a href="https://android.googlesource.com/device/huawei/angler/+/cf92cd8/releasetools.py#29">releasetools.py</a> -<br />
 uses &quot;Huawei Bootloader packed image format&quot; instead</li>
 </ul>
 </li>
 </ul>
 <hr />
-<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory
-images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images
-for Nexus and Pixel Devices</a> on
-the Google Developers site. Note that the codenames on that page may be
-different than the ones that are written in the list above. That's because the
-Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)
-but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because
-that is how the original <code>bootloader-*.img</code> files are identified. For most
+<p>The <code>bootloader-*.img</code> samples referenced above originally come from factory<br />
+images packed in ZIP archives that can be found on the page <a href="https://developers.google.com/android/images">Factory Images<br />
+for Nexus and Pixel Devices</a> on<br />
+the Google Developers site. Note that the codenames on that page may be<br />
+different than the ones that are written in the list above. That's because the<br />
+Google page indicates <strong>ROM codenames</strong> in headings (e.g. &quot;occam&quot; for Nexus 4)<br />
+but the above list uses <strong>model codenames</strong> (e.g. &quot;mako&quot; for Nexus 4) because<br />
+that is how the original <code>bootloader-*.img</code> files are identified. For most<br />
 devices, however, these code names are the same.</p>
 </p>
             </div>
@@ -607,7 +607,7 @@ <h3>android_bootldr_qcom.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/cpp_stl_11.html b/android_dto/cpp_stl_11.html
index a4fb2166c..66d3d1440 100644
--- a/android_dto/cpp_stl_11.html
+++ b/android_dto/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -631,7 +631,7 @@ <h3>android_dto.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/cpp_stl_98.html b/android_dto/cpp_stl_98.html
index 58c4514f7..fd3ae8240 100644
--- a/android_dto/cpp_stl_98.html
+++ b/android_dto/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -663,7 +663,7 @@ <h3>android_dto.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/csharp.html b/android_dto/csharp.html
index aebd6d1b1..ad67758aa 100644
--- a/android_dto/csharp.html
+++ b/android_dto/csharp.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -514,7 +514,7 @@ <h3>AndroidDto.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/go.html b/android_dto/go.html
index ce2db3de6..daebffd9b 100644
--- a/android_dto/go.html
+++ b/android_dto/go.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -513,7 +513,7 @@ <h3>android_dto.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/graphviz.html b/android_dto/graphviz.html
index 602183d38..b79031705 100644
--- a/android_dto/graphviz.html
+++ b/android_dto/graphviz.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -313,7 +313,7 @@ <h3>android_dto.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/index.html b/android_dto/index.html
index 67405f745..c5039763f 100644
--- a/android_dto/index.html
+++ b/android_dto/index.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -325,7 +325,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/java.html b/android_dto/java.html
index 623536e2e..48923a5ac 100644
--- a/android_dto/java.html
+++ b/android_dto/java.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -519,7 +519,7 @@ <h3>AndroidDto.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/javascript.html b/android_dto/javascript.html
index e7ffc016c..c1db16fd8 100644
--- a/android_dto/javascript.html
+++ b/android_dto/javascript.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -452,7 +452,7 @@ <h3>AndroidDto.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/lua.html b/android_dto/lua.html
index 92594718d..51bcf5977 100644
--- a/android_dto/lua.html
+++ b/android_dto/lua.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -378,7 +378,7 @@ <h3>android_dto.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/nim.html b/android_dto/nim.html
index 8e83a75af..2a4012e26 100644
--- a/android_dto/nim.html
+++ b/android_dto/nim.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -437,7 +437,7 @@ <h3>android_dto.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/perl.html b/android_dto/perl.html
index a0b5d2167..73a7c681c 100644
--- a/android_dto/perl.html
+++ b/android_dto/perl.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -471,7 +471,7 @@ <h3>AndroidDto.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/php.html b/android_dto/php.html
index 2775a229c..a246ac307 100644
--- a/android_dto/php.html
+++ b/android_dto/php.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -426,7 +426,7 @@ <h3>AndroidDto.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/python.html b/android_dto/python.html
index 54c7c39d6..71e5e16d9 100644
--- a/android_dto/python.html
+++ b/android_dto/python.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -390,7 +390,7 @@ <h3>android_dto.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_dto/ruby.html b/android_dto/ruby.html
index 27bc014f9..18c5ea576 100644
--- a/android_dto/ruby.html
+++ b/android_dto/ruby.html
@@ -105,12 +105,12 @@ <h1>Android DTB/DTBO Partition:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with
-dtb/dtbo files. Used only when there is a separate unique partition
-(dtb, dtbo) on an android device to organize device tree files.
-The format consists of a header with info about size and number
-of device tree entries and the entries themselves. This format
-description could be used to extract device tree entries from a
+                <p><p>Format for Android DTB/DTBO partitions. It's kind of archive with<br />
+dtb/dtbo files. Used only when there is a separate unique partition<br />
+(dtb, dtbo) on an android device to organize device tree files.<br />
+The format consists of a header with info about size and number<br />
+of device tree entries and the entries themselves. This format<br />
+description could be used to extract device tree entries from a<br />
 partition images and decompile them with dtc (device tree compiler).</p>
 </p>
             </div>
@@ -435,7 +435,7 @@ <h3>android_dto.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/cpp_stl_11.html b/android_img/cpp_stl_11.html
index 5c47cbff9..ad715ec5f 100644
--- a/android_img/cpp_stl_11.html
+++ b/android_img/cpp_stl_11.html
@@ -1026,7 +1026,7 @@ <h3>android_img.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/cpp_stl_98.html b/android_img/cpp_stl_98.html
index 22868d06f..f370c6f27 100644
--- a/android_img/cpp_stl_98.html
+++ b/android_img/cpp_stl_98.html
@@ -1076,7 +1076,7 @@ <h3>android_img.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/csharp.html b/android_img/csharp.html
index d560af607..b62b1907c 100644
--- a/android_img/csharp.html
+++ b/android_img/csharp.html
@@ -759,7 +759,7 @@ <h3>AndroidImg.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/go.html b/android_img/go.html
index 5fc34bcfb..fffcd0d8c 100644
--- a/android_img/go.html
+++ b/android_img/go.html
@@ -823,7 +823,7 @@ <h3>android_img.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/graphviz.html b/android_img/graphviz.html
index 82444198c..1e7b76720 100644
--- a/android_img/graphviz.html
+++ b/android_img/graphviz.html
@@ -433,7 +433,7 @@ <h3>android_img.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/index.html b/android_img/index.html
index e5c3d8336..bb2672b43 100644
--- a/android_img/index.html
+++ b/android_img/index.html
@@ -362,7 +362,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/java.html b/android_img/java.html
index 91aa12070..357d3832d 100644
--- a/android_img/java.html
+++ b/android_img/java.html
@@ -686,7 +686,7 @@ <h3>AndroidImg.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/javascript.html b/android_img/javascript.html
index 4a4db04fc..2cd904b68 100644
--- a/android_img/javascript.html
+++ b/android_img/javascript.html
@@ -585,7 +585,7 @@ <h3>AndroidImg.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/lua.html b/android_img/lua.html
index 8efdd3ca8..68e9b564c 100644
--- a/android_img/lua.html
+++ b/android_img/lua.html
@@ -554,7 +554,7 @@ <h3>android_img.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/nim.html b/android_img/nim.html
index d45fcdaff..0405dcb6a 100644
--- a/android_img/nim.html
+++ b/android_img/nim.html
@@ -626,7 +626,7 @@ <h3>android_img.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/perl.html b/android_img/perl.html
index 4ad318314..f080b2ff9 100644
--- a/android_img/perl.html
+++ b/android_img/perl.html
@@ -695,7 +695,7 @@ <h3>AndroidImg.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/php.html b/android_img/php.html
index 1aeefbe37..49c5cbd1c 100644
--- a/android_img/php.html
+++ b/android_img/php.html
@@ -550,7 +550,7 @@ <h3>AndroidImg.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/python.html b/android_img/python.html
index 5de164709..846505d22 100644
--- a/android_img/python.html
+++ b/android_img/python.html
@@ -546,7 +546,7 @@ <h3>android_img.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_img/ruby.html b/android_img/ruby.html
index 5b65818d0..a4b3f5dcb 100644
--- a/android_img/ruby.html
+++ b/android_img/ruby.html
@@ -529,7 +529,7 @@ <h3>android_img.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/cpp_stl_11.html b/android_nanoapp_header/cpp_stl_11.html
index 63e6312df..b7964b555 100644
--- a/android_nanoapp_header/cpp_stl_11.html
+++ b/android_nanoapp_header/cpp_stl_11.html
@@ -492,7 +492,7 @@ <h3>android_nanoapp_header.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/cpp_stl_98.html b/android_nanoapp_header/cpp_stl_98.html
index 57ebca561..186b2b786 100644
--- a/android_nanoapp_header/cpp_stl_98.html
+++ b/android_nanoapp_header/cpp_stl_98.html
@@ -500,7 +500,7 @@ <h3>android_nanoapp_header.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/csharp.html b/android_nanoapp_header/csharp.html
index 3fd899038..db671fb77 100644
--- a/android_nanoapp_header/csharp.html
+++ b/android_nanoapp_header/csharp.html
@@ -411,7 +411,7 @@ <h3>AndroidNanoappHeader.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/go.html b/android_nanoapp_header/go.html
index 4e8320196..7c0c836fd 100644
--- a/android_nanoapp_header/go.html
+++ b/android_nanoapp_header/go.html
@@ -379,7 +379,7 @@ <h3>android_nanoapp_header.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/graphviz.html b/android_nanoapp_header/graphviz.html
index 6d02edf5f..dce189959 100644
--- a/android_nanoapp_header/graphviz.html
+++ b/android_nanoapp_header/graphviz.html
@@ -292,7 +292,7 @@ <h3>android_nanoapp_header.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/index.html b/android_nanoapp_header/index.html
index 5c3d2f562..90bb23fd0 100644
--- a/android_nanoapp_header/index.html
+++ b/android_nanoapp_header/index.html
@@ -281,7 +281,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/java.html b/android_nanoapp_header/java.html
index ba498b59a..360180045 100644
--- a/android_nanoapp_header/java.html
+++ b/android_nanoapp_header/java.html
@@ -398,7 +398,7 @@ <h3>AndroidNanoappHeader.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/javascript.html b/android_nanoapp_header/javascript.html
index 752efbbe0..7f1a386aa 100644
--- a/android_nanoapp_header/javascript.html
+++ b/android_nanoapp_header/javascript.html
@@ -367,7 +367,7 @@ <h3>AndroidNanoappHeader.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/lua.html b/android_nanoapp_header/lua.html
index 6e3a3297a..93c295214 100644
--- a/android_nanoapp_header/lua.html
+++ b/android_nanoapp_header/lua.html
@@ -324,7 +324,7 @@ <h3>android_nanoapp_header.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/nim.html b/android_nanoapp_header/nim.html
index 93263b4a3..b99391138 100644
--- a/android_nanoapp_header/nim.html
+++ b/android_nanoapp_header/nim.html
@@ -341,7 +341,7 @@ <h3>android_nanoapp_header.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/perl.html b/android_nanoapp_header/perl.html
index 4afbeafcb..460bada56 100644
--- a/android_nanoapp_header/perl.html
+++ b/android_nanoapp_header/perl.html
@@ -370,7 +370,7 @@ <h3>AndroidNanoappHeader.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/php.html b/android_nanoapp_header/php.html
index 331485f8a..4de539b1b 100644
--- a/android_nanoapp_header/php.html
+++ b/android_nanoapp_header/php.html
@@ -327,7 +327,7 @@ <h3>AndroidNanoappHeader.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/python.html b/android_nanoapp_header/python.html
index 39b00f1b6..364d38e04 100644
--- a/android_nanoapp_header/python.html
+++ b/android_nanoapp_header/python.html
@@ -360,7 +360,7 @@ <h3>android_nanoapp_header.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_nanoapp_header/ruby.html b/android_nanoapp_header/ruby.html
index 66c08bbf8..069cd8724 100644
--- a/android_nanoapp_header/ruby.html
+++ b/android_nanoapp_header/ruby.html
@@ -355,7 +355,7 @@ <h3>android_nanoapp_header.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/cpp_stl_11.html b/android_opengl_shaders_cache/cpp_stl_11.html
index e4437e973..c5358e1a8 100644
--- a/android_opengl_shaders_cache/cpp_stl_11.html
+++ b/android_opengl_shaders_cache/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -665,7 +665,7 @@ <h3>android_opengl_shaders_cache.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/cpp_stl_98.html b/android_opengl_shaders_cache/cpp_stl_98.html
index f01bbe2f9..e63057344 100644
--- a/android_opengl_shaders_cache/cpp_stl_98.html
+++ b/android_opengl_shaders_cache/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -718,7 +718,7 @@ <h3>android_opengl_shaders_cache.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/csharp.html b/android_opengl_shaders_cache/csharp.html
index 82c8b846f..4883d396a 100644
--- a/android_opengl_shaders_cache/csharp.html
+++ b/android_opengl_shaders_cache/csharp.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -500,7 +500,7 @@ <h3>AndroidOpenglShadersCache.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/go.html b/android_opengl_shaders_cache/go.html
index dd484840f..4557f9d97 100644
--- a/android_opengl_shaders_cache/go.html
+++ b/android_opengl_shaders_cache/go.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -510,7 +510,7 @@ <h3>android_opengl_shaders_cache.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/graphviz.html b/android_opengl_shaders_cache/graphviz.html
index 41e5372b2..8e95ed143 100644
--- a/android_opengl_shaders_cache/graphviz.html
+++ b/android_opengl_shaders_cache/graphviz.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -326,7 +326,7 @@ <h3>android_opengl_shaders_cache.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/index.html b/android_opengl_shaders_cache/index.html
index 0fff194d4..65cd1ea1a 100644
--- a/android_opengl_shaders_cache/index.html
+++ b/android_opengl_shaders_cache/index.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -322,7 +322,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/java.html b/android_opengl_shaders_cache/java.html
index 204254365..4466f1991 100644
--- a/android_opengl_shaders_cache/java.html
+++ b/android_opengl_shaders_cache/java.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -525,7 +525,7 @@ <h3>AndroidOpenglShadersCache.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/javascript.html b/android_opengl_shaders_cache/javascript.html
index 2538c5303..09faed01a 100644
--- a/android_opengl_shaders_cache/javascript.html
+++ b/android_opengl_shaders_cache/javascript.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -424,7 +424,7 @@ <h3>AndroidOpenglShadersCache.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/lua.html b/android_opengl_shaders_cache/lua.html
index 0abca38be..19d905068 100644
--- a/android_opengl_shaders_cache/lua.html
+++ b/android_opengl_shaders_cache/lua.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -367,7 +367,7 @@ <h3>android_opengl_shaders_cache.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/nim.html b/android_opengl_shaders_cache/nim.html
index eec10d1f3..b1bfd81c9 100644
--- a/android_opengl_shaders_cache/nim.html
+++ b/android_opengl_shaders_cache/nim.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -414,7 +414,7 @@ <h3>android_opengl_shaders_cache.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/perl.html b/android_opengl_shaders_cache/perl.html
index 2aba297bb..5420be600 100644
--- a/android_opengl_shaders_cache/perl.html
+++ b/android_opengl_shaders_cache/perl.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -543,7 +543,7 @@ <h3>AndroidOpenglShadersCache.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/php.html b/android_opengl_shaders_cache/php.html
index cacb87b35..2f03d0d45 100644
--- a/android_opengl_shaders_cache/php.html
+++ b/android_opengl_shaders_cache/php.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -399,7 +399,7 @@ <h3>AndroidOpenglShadersCache.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/python.html b/android_opengl_shaders_cache/python.html
index ced09219d..1bc4759b1 100644
--- a/android_opengl_shaders_cache/python.html
+++ b/android_opengl_shaders_cache/python.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -392,7 +392,7 @@ <h3>android_opengl_shaders_cache.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_opengl_shaders_cache/ruby.html b/android_opengl_shaders_cache/ruby.html
index 474bfb73f..392dc7918 100644
--- a/android_opengl_shaders_cache/ruby.html
+++ b/android_opengl_shaders_cache/ruby.html
@@ -105,7 +105,7 @@ <h1>com.android.opengl.shaders_cache file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders
+                <p><p>Android apps using directly or indirectly OpenGL cache compiled shaders<br />
 into com.android.opengl.shaders_cache file.</p>
 </p>
             </div>
@@ -414,7 +414,7 @@ <h3>android_opengl_shaders_cache.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/cpp_stl_11.html b/android_sparse/cpp_stl_11.html
index 9aade1ba6..430003961 100644
--- a/android_sparse/cpp_stl_11.html
+++ b/android_sparse/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -842,7 +842,7 @@ <h3>android_sparse.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/cpp_stl_98.html b/android_sparse/cpp_stl_98.html
index 6b1d934bd..026d99555 100644
--- a/android_sparse/cpp_stl_98.html
+++ b/android_sparse/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -910,7 +910,7 @@ <h3>android_sparse.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/csharp.html b/android_sparse/csharp.html
index c83f2d836..56a4048ad 100644
--- a/android_sparse/csharp.html
+++ b/android_sparse/csharp.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -659,7 +659,7 @@ <h3>AndroidSparse.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/go.html b/android_sparse/go.html
index fc80b1e11..e0e7038c4 100644
--- a/android_sparse/go.html
+++ b/android_sparse/go.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -694,7 +694,7 @@ <h3>android_sparse.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/index.html b/android_sparse/index.html
index 2f401108a..7ffc77c74 100644
--- a/android_sparse/index.html
+++ b/android_sparse/index.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -377,7 +377,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/java.html b/android_sparse/java.html
index d83440450..3758c3f68 100644
--- a/android_sparse/java.html
+++ b/android_sparse/java.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -671,7 +671,7 @@ <h3>AndroidSparse.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/javascript.html b/android_sparse/javascript.html
index 573b645d4..95f0281ec 100644
--- a/android_sparse/javascript.html
+++ b/android_sparse/javascript.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -538,7 +538,7 @@ <h3>AndroidSparse.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/lua.html b/android_sparse/lua.html
index 795a358e1..bc5c3a68d 100644
--- a/android_sparse/lua.html
+++ b/android_sparse/lua.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -466,7 +466,7 @@ <h3>android_sparse.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/php.html b/android_sparse/php.html
index 181cd2754..2c8d82837 100644
--- a/android_sparse/php.html
+++ b/android_sparse/php.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -504,7 +504,7 @@ <h3>AndroidSparse.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/python.html b/android_sparse/python.html
index 02a981110..18e613c96 100644
--- a/android_sparse/python.html
+++ b/android_sparse/python.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -469,7 +469,7 @@ <h3>android_sparse.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_sparse/ruby.html b/android_sparse/ruby.html
index cd54bd7ee..ddf9e4ab1 100644
--- a/android_sparse/ruby.html
+++ b/android_sparse/ruby.html
@@ -105,8 +105,8 @@ <h1>Android sparse image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Android sparse format is a format to more efficiently store files
-for for example firmware updates to save on bandwidth. Files in sparse
+                <p><p>The Android sparse format is a format to more efficiently store files<br />
+for for example firmware updates to save on bandwidth. Files in sparse<br />
 format first have to be converted back to their original format.</p>
 <p>A tool to create images for testing can be found in the Android source code tree:</p>
 <p><a href="https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse">https://android.googlesource.com/platform/system/core/+/e8d02c50d7/libsparse</a> - <code>img2simg.c</code></p>
@@ -496,7 +496,7 @@ <h3>android_sparse.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/cpp_stl_11.html b/android_super/cpp_stl_11.html
index 057364d02..b9ce17798 100644
--- a/android_super/cpp_stl_11.html
+++ b/android_super/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -1061,7 +1061,7 @@ <h3>android_super.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/cpp_stl_98.html b/android_super/cpp_stl_98.html
index e929092d5..c955a08fb 100644
--- a/android_super/cpp_stl_98.html
+++ b/android_super/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -1189,7 +1189,7 @@ <h3>android_super.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/csharp.html b/android_super/csharp.html
index f477a44f5..0442d229f 100644
--- a/android_super/csharp.html
+++ b/android_super/csharp.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -796,7 +796,7 @@ <h3>AndroidSuper.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/go.html b/android_super/go.html
index d13af9c26..ab3e37706 100644
--- a/android_super/go.html
+++ b/android_super/go.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -938,7 +938,7 @@ <h3>android_super.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/graphviz.html b/android_super/graphviz.html
index bf55f3ef8..2324df888 100644
--- a/android_super/graphviz.html
+++ b/android_super/graphviz.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -432,7 +432,7 @@ <h3>android_super.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/index.html b/android_super/index.html
index a3f15f66c..d1fc508bf 100644
--- a/android_super/index.html
+++ b/android_super/index.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -465,7 +465,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/java.html b/android_super/java.html
index f50b4f926..32e6a2ed4 100644
--- a/android_super/java.html
+++ b/android_super/java.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -852,7 +852,7 @@ <h3>AndroidSuper.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/javascript.html b/android_super/javascript.html
index dcee25323..fc7eeb3cc 100644
--- a/android_super/javascript.html
+++ b/android_super/javascript.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -612,7 +612,7 @@ <h3>AndroidSuper.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/lua.html b/android_super/lua.html
index 8a7c398eb..b766bb36c 100644
--- a/android_super/lua.html
+++ b/android_super/lua.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -543,7 +543,7 @@ <h3>android_super.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/nim.html b/android_super/nim.html
index cc61f006c..1a197885a 100644
--- a/android_super/nim.html
+++ b/android_super/nim.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -668,7 +668,7 @@ <h3>android_super.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/perl.html b/android_super/perl.html
index 3f49c3a98..cf7932a1f 100644
--- a/android_super/perl.html
+++ b/android_super/perl.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -958,7 +958,7 @@ <h3>AndroidSuper.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/php.html b/android_super/php.html
index 2ee5c4058..16724d193 100644
--- a/android_super/php.html
+++ b/android_super/php.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -648,7 +648,7 @@ <h3>AndroidSuper.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/python.html b/android_super/python.html
index b70066427..c1ac24ee4 100644
--- a/android_super/python.html
+++ b/android_super/python.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -549,7 +549,7 @@ <h3>android_super.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/android_super/ruby.html b/android_super/ruby.html
index e7b08c169..258ce7e32 100644
--- a/android_super/ruby.html
+++ b/android_super/ruby.html
@@ -105,10 +105,10 @@ <h1>Android Dynamic Partitions metadata:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which
-is what it calls a disk partition that holds one or more Dynamic Partitions.
-Dynamic Partitions do more or less the same thing that LVM does on Linux,
-allowing Android to map ranges of non-contiguous extents to a single logical
+                <p><p>The metadata stored by Android at the beginning of a &quot;super&quot; partition, which<br />
+is what it calls a disk partition that holds one or more Dynamic Partitions.<br />
+Dynamic Partitions do more or less the same thing that LVM does on Linux,<br />
+allowing Android to map ranges of non-contiguous extents to a single logical<br />
 device. This metadata holds that mapping.</p>
 </p>
             </div>
@@ -604,7 +604,7 @@ <h3>android_super.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/cpp_stl_11.html b/apm_partition_table/cpp_stl_11.html
index 9d51a7ad2..a79b9bac5 100644
--- a/apm_partition_table/cpp_stl_11.html
+++ b/apm_partition_table/cpp_stl_11.html
@@ -726,7 +726,7 @@ <h3>apm_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/cpp_stl_98.html b/apm_partition_table/cpp_stl_98.html
index 426d692ca..1562cfc0c 100644
--- a/apm_partition_table/cpp_stl_98.html
+++ b/apm_partition_table/cpp_stl_98.html
@@ -761,7 +761,7 @@ <h3>apm_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/csharp.html b/apm_partition_table/csharp.html
index 70538d8b4..d89f1fb18 100644
--- a/apm_partition_table/csharp.html
+++ b/apm_partition_table/csharp.html
@@ -589,7 +589,7 @@ <h3>ApmPartitionTable.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/go.html b/apm_partition_table/go.html
index e77b7fe1a..1ae063748 100644
--- a/apm_partition_table/go.html
+++ b/apm_partition_table/go.html
@@ -696,7 +696,7 @@ <h3>apm_partition_table.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/graphviz.html b/apm_partition_table/graphviz.html
index e06a0f1d6..0950a1b4d 100644
--- a/apm_partition_table/graphviz.html
+++ b/apm_partition_table/graphviz.html
@@ -350,7 +350,7 @@ <h3>apm_partition_table.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/index.html b/apm_partition_table/index.html
index 19cbbd5da..d51fa492f 100644
--- a/apm_partition_table/index.html
+++ b/apm_partition_table/index.html
@@ -358,7 +358,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/java.html b/apm_partition_table/java.html
index 21a158bf9..706bb0cc6 100644
--- a/apm_partition_table/java.html
+++ b/apm_partition_table/java.html
@@ -561,7 +561,7 @@ <h3>ApmPartitionTable.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/javascript.html b/apm_partition_table/javascript.html
index fb3a6a7cb..a2c04da4c 100644
--- a/apm_partition_table/javascript.html
+++ b/apm_partition_table/javascript.html
@@ -499,7 +499,7 @@ <h3>ApmPartitionTable.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/lua.html b/apm_partition_table/lua.html
index 9cbe50510..fe09d8b69 100644
--- a/apm_partition_table/lua.html
+++ b/apm_partition_table/lua.html
@@ -441,7 +441,7 @@ <h3>apm_partition_table.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/nim.html b/apm_partition_table/nim.html
index 133f8153e..cc880da5c 100644
--- a/apm_partition_table/nim.html
+++ b/apm_partition_table/nim.html
@@ -508,7 +508,7 @@ <h3>apm_partition_table.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/perl.html b/apm_partition_table/perl.html
index 9510e4b45..b6651f22c 100644
--- a/apm_partition_table/perl.html
+++ b/apm_partition_table/perl.html
@@ -532,7 +532,7 @@ <h3>ApmPartitionTable.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/php.html b/apm_partition_table/php.html
index d7690fc06..eed161b0d 100644
--- a/apm_partition_table/php.html
+++ b/apm_partition_table/php.html
@@ -476,7 +476,7 @@ <h3>ApmPartitionTable.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/python.html b/apm_partition_table/python.html
index 3f5542574..6683e8906 100644
--- a/apm_partition_table/python.html
+++ b/apm_partition_table/python.html
@@ -451,7 +451,7 @@ <h3>apm_partition_table.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apm_partition_table/ruby.html b/apm_partition_table/ruby.html
index 95dc6149c..8ea19f401 100644
--- a/apm_partition_table/ruby.html
+++ b/apm_partition_table/ruby.html
@@ -478,7 +478,7 @@ <h3>apm_partition_table.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/cpp_stl_11.html b/apple_single_double/cpp_stl_11.html
index 8dd01dd00..7e4fbd8b6 100644
--- a/apple_single_double/cpp_stl_11.html
+++ b/apple_single_double/cpp_stl_11.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -714,7 +714,7 @@ <h3>apple_single_double.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/cpp_stl_98.html b/apple_single_double/cpp_stl_98.html
index ad3afbfa4..876424872 100644
--- a/apple_single_double/cpp_stl_98.html
+++ b/apple_single_double/cpp_stl_98.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -755,7 +755,7 @@ <h3>apple_single_double.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/csharp.html b/apple_single_double/csharp.html
index ebcaa31f1..c48fe87c7 100644
--- a/apple_single_double/csharp.html
+++ b/apple_single_double/csharp.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -571,7 +571,7 @@ <h3>AppleSingleDouble.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/go.html b/apple_single_double/go.html
index 466f727da..f57c83060 100644
--- a/apple_single_double/go.html
+++ b/apple_single_double/go.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -575,7 +575,7 @@ <h3>apple_single_double.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/graphviz.html b/apple_single_double/graphviz.html
index df88bb292..ed648a530 100644
--- a/apple_single_double/graphviz.html
+++ b/apple_single_double/graphviz.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -354,7 +354,7 @@ <h3>apple_single_double.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/index.html b/apple_single_double/index.html
index 196524ac7..837ab0dac 100644
--- a/apple_single_double/index.html
+++ b/apple_single_double/index.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -406,7 +406,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/java.html b/apple_single_double/java.html
index 1c563131b..c3a5a3b1d 100644
--- a/apple_single_double/java.html
+++ b/apple_single_double/java.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -609,7 +609,7 @@ <h3>AppleSingleDouble.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/javascript.html b/apple_single_double/javascript.html
index 727de6e38..7b64ef3b6 100644
--- a/apple_single_double/javascript.html
+++ b/apple_single_double/javascript.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -516,7 +516,7 @@ <h3>AppleSingleDouble.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/lua.html b/apple_single_double/lua.html
index de6e70a0a..3d473ef64 100644
--- a/apple_single_double/lua.html
+++ b/apple_single_double/lua.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -438,7 +438,7 @@ <h3>apple_single_double.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/nim.html b/apple_single_double/nim.html
index 4d0935f53..3fd5d3111 100644
--- a/apple_single_double/nim.html
+++ b/apple_single_double/nim.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -486,7 +486,7 @@ <h3>apple_single_double.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/perl.html b/apple_single_double/perl.html
index 07e588c30..78fadc409 100644
--- a/apple_single_double/perl.html
+++ b/apple_single_double/perl.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -557,7 +557,7 @@ <h3>AppleSingleDouble.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/php.html b/apple_single_double/php.html
index 4f30edc4a..2f6324bd3 100644
--- a/apple_single_double/php.html
+++ b/apple_single_double/php.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -483,7 +483,7 @@ <h3>AppleSingleDouble.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/python.html b/apple_single_double/python.html
index c088cd220..b9bad61d7 100644
--- a/apple_single_double/python.html
+++ b/apple_single_double/python.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -462,7 +462,7 @@ <h3>apple_single_double.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/apple_single_double/ruby.html b/apple_single_double/ruby.html
index e1b356749..a9679f845 100644
--- a/apple_single_double/ruby.html
+++ b/apple_single_double/ruby.html
@@ -105,23 +105,23 @@ <h1>AppleSingle / AppleDouble:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>AppleSingle and AppleDouble files are used by certain Mac
-applications (e.g. Finder) to store Mac-specific file attributes on
+                <p><p>AppleSingle and AppleDouble files are used by certain Mac<br />
+applications (e.g. Finder) to store Mac-specific file attributes on<br />
 filesystems that do not support that.</p>
-<p>Syntactically, both formats are the same, the only difference is how
+<p>Syntactically, both formats are the same, the only difference is how<br />
 they are being used:</p>
 <ul>
-<li>AppleSingle means that only one file will be created on external
-filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple
+<li>AppleSingle means that only one file will be created on external<br />
+filesystem that will hold both the data (AKA &quot;data fork&quot; in Apple<br />
 terminology), and the attributes (AKA &quot;resource fork&quot;).</li>
-<li>AppleDouble means that two files will be created: a normal file
-that keeps the data (&quot;data fork&quot;) is kept separately from an
-auxiliary file that contains attributes (&quot;resource fork&quot;), which
-is kept with the same name, but starting with an extra dot and
+<li>AppleDouble means that two files will be created: a normal file<br />
+that keeps the data (&quot;data fork&quot;) is kept separately from an<br />
+auxiliary file that contains attributes (&quot;resource fork&quot;), which<br />
+is kept with the same name, but starting with an extra dot and<br />
 underscore <code>._</code> to keep it hidden.</li>
 </ul>
-<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep
-compatibility with other OSes, as virtually nobody outside of Mac
+<p>In modern practice (Mac OS X), Finder only uses AppleDouble to keep<br />
+compatibility with other OSes, as virtually nobody outside of Mac<br />
 understands how to access data in AppleSingle container.</p>
 </p>
             </div>
@@ -488,7 +488,7 @@ <h3>apple_single_double.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/cpp_stl_11.html b/asn1_der/cpp_stl_11.html
index 13ab231a7..09cd077d4 100644
--- a/asn1_der/cpp_stl_11.html
+++ b/asn1_der/cpp_stl_11.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -868,7 +868,7 @@ <h3>asn1_der.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/cpp_stl_98.html b/asn1_der/cpp_stl_98.html
index caa53715d..afaa2c7d1 100644
--- a/asn1_der/cpp_stl_98.html
+++ b/asn1_der/cpp_stl_98.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -921,7 +921,7 @@ <h3>asn1_der.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/csharp.html b/asn1_der/csharp.html
index f6a58cb74..a0b2484a2 100644
--- a/asn1_der/csharp.html
+++ b/asn1_der/csharp.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -657,7 +657,7 @@ <h3>Asn1Der.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/go.html b/asn1_der/go.html
index c67f9bac2..40038c72f 100644
--- a/asn1_der/go.html
+++ b/asn1_der/go.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -707,7 +707,7 @@ <h3>asn1_der.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/graphviz.html b/asn1_der/graphviz.html
index 5b43267ba..e0a47bd3f 100644
--- a/asn1_der/graphviz.html
+++ b/asn1_der/graphviz.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -399,7 +399,7 @@ <h3>asn1_der.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/index.html b/asn1_der/index.html
index 3b057f20e..7b129e41a 100644
--- a/asn1_der/index.html
+++ b/asn1_der/index.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -405,7 +405,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/java.html b/asn1_der/java.html
index 363a3d43d..92a8a9d69 100644
--- a/asn1_der/java.html
+++ b/asn1_der/java.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -689,7 +689,7 @@ <h3>Asn1Der.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/javascript.html b/asn1_der/javascript.html
index d5ca4f847..d8d765148 100644
--- a/asn1_der/javascript.html
+++ b/asn1_der/javascript.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -583,7 +583,7 @@ <h3>Asn1Der.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/lua.html b/asn1_der/lua.html
index b9c71bf55..db14345d7 100644
--- a/asn1_der/lua.html
+++ b/asn1_der/lua.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -510,7 +510,7 @@ <h3>asn1_der.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/nim.html b/asn1_der/nim.html
index f5bff5777..19c13e3b9 100644
--- a/asn1_der/nim.html
+++ b/asn1_der/nim.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -557,7 +557,7 @@ <h3>asn1_der.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/perl.html b/asn1_der/perl.html
index 5f24bf998..298f9776c 100644
--- a/asn1_der/perl.html
+++ b/asn1_der/perl.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -649,7 +649,7 @@ <h3>Asn1Der.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/php.html b/asn1_der/php.html
index ac056ceaa..2e06cd296 100644
--- a/asn1_der/php.html
+++ b/asn1_der/php.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -520,7 +520,7 @@ <h3>Asn1Der.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/python.html b/asn1_der/python.html
index c72e2fc43..62aee6e6f 100644
--- a/asn1_der/python.html
+++ b/asn1_der/python.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -530,7 +530,7 @@ <h3>asn1_der.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/asn1_der/ruby.html b/asn1_der/ruby.html
index b491d9a26..94c85ac00 100644
--- a/asn1_der/ruby.html
+++ b/asn1_der/ruby.html
@@ -105,21 +105,21 @@ <h1>ASN.1 DER (Abstract Syntax Notation One, Distinguished Encoding Rules):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding
-Rules) is a standard-backed serialization scheme used in many
-different use-cases. Particularly popular usage scenarios are X.509
+                <p><p>ASN.1 (Abstract Syntax Notation One) DER (Distinguished Encoding<br />
+Rules) is a standard-backed serialization scheme used in many<br />
+different use-cases. Particularly popular usage scenarios are X.509<br />
 certificates and some telecommunication / networking protocols.</p>
-<p>DER is self-describing encoding scheme which allows representation
-of simple, atomic data elements, such as strings and numbers, and
+<p>DER is self-describing encoding scheme which allows representation<br />
+of simple, atomic data elements, such as strings and numbers, and<br />
 complex objects, such as sequences of other elements.</p>
-<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on
-being non-ambiguous: there's always exactly one canonical way to
+<p>DER is a subset of BER (Basic Encoding Rules), with an emphasis on<br />
+being non-ambiguous: there's always exactly one canonical way to<br />
 encode a data structure defined in terms of ASN.1 using DER.</p>
-<p>This spec allows full parsing of format syntax, but to understand
-the semantics, one would typically require a dictionary of Object
-Identifiers (OIDs), to match OID bodies against some human-readable
-list of constants. OIDs are covered by many different standards,
-so typically it's simpler to use a pre-compiled list of them, such
+<p>This spec allows full parsing of format syntax, but to understand<br />
+the semantics, one would typically require a dictionary of Object<br />
+Identifiers (OIDs), to match OID bodies against some human-readable<br />
+list of constants. OIDs are covered by many different standards,<br />
+so typically it's simpler to use a pre-compiled list of them, such<br />
 as:</p>
 <ul>
 <li><a href="https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg">https://www.cs.auckland.ac.nz/~pgut001/dumpasn1.cfg</a></li>
@@ -533,7 +533,7 @@ <h3>asn1_der.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/cpp_stl_11.html b/au/cpp_stl_11.html
index 874a6dda1..0e2bf8a7d 100644
--- a/au/cpp_stl_11.html
+++ b/au/cpp_stl_11.html
@@ -604,7 +604,7 @@ <h3>au.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/cpp_stl_98.html b/au/cpp_stl_98.html
index 6e053b22e..fff4079eb 100644
--- a/au/cpp_stl_98.html
+++ b/au/cpp_stl_98.html
@@ -624,7 +624,7 @@ <h3>au.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/csharp.html b/au/csharp.html
index 5af62cc39..ce4eb090a 100644
--- a/au/csharp.html
+++ b/au/csharp.html
@@ -519,7 +519,7 @@ <h3>Au.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/go.html b/au/go.html
index ab82399b8..1d26ff519 100644
--- a/au/go.html
+++ b/au/go.html
@@ -490,7 +490,7 @@ <h3>au.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/graphviz.html b/au/graphviz.html
index f69aef79d..7b9db8965 100644
--- a/au/graphviz.html
+++ b/au/graphviz.html
@@ -326,7 +326,7 @@ <h3>au.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/index.html b/au/index.html
index 56db56eed..0ed8a71b9 100644
--- a/au/index.html
+++ b/au/index.html
@@ -437,7 +437,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/java.html b/au/java.html
index b206ca4a0..9a0cf616f 100644
--- a/au/java.html
+++ b/au/java.html
@@ -522,7 +522,7 @@ <h3>Au.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/javascript.html b/au/javascript.html
index ad9082b95..597be5e38 100644
--- a/au/javascript.html
+++ b/au/javascript.html
@@ -495,7 +495,7 @@ <h3>Au.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/lua.html b/au/lua.html
index 272d755f6..9c325aab1 100644
--- a/au/lua.html
+++ b/au/lua.html
@@ -417,7 +417,7 @@ <h3>au.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/nim.html b/au/nim.html
index 37be71dce..f4c02aadc 100644
--- a/au/nim.html
+++ b/au/nim.html
@@ -439,7 +439,7 @@ <h3>au.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/perl.html b/au/perl.html
index 09ac57407..67b9f0669 100644
--- a/au/perl.html
+++ b/au/perl.html
@@ -450,7 +450,7 @@ <h3>Au.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/php.html b/au/php.html
index 4dcd674ad..b3f772af1 100644
--- a/au/php.html
+++ b/au/php.html
@@ -513,7 +513,7 @@ <h3>Au.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/python.html b/au/python.html
index 97449a244..cef030704 100644
--- a/au/python.html
+++ b/au/python.html
@@ -446,7 +446,7 @@ <h3>au.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/au/ruby.html b/au/ruby.html
index b0383665e..3b3ee1d0e 100644
--- a/au/ruby.html
+++ b/au/ruby.html
@@ -456,7 +456,7 @@ <h3>au.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/cpp_stl_11.html b/avantes_roh60/cpp_stl_11.html
index 162046940..93269c0bb 100644
--- a/avantes_roh60/cpp_stl_11.html
+++ b/avantes_roh60/cpp_stl_11.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -532,7 +532,7 @@ <h3>avantes_roh60.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/cpp_stl_98.html b/avantes_roh60/cpp_stl_98.html
index b63421e19..e28f89511 100644
--- a/avantes_roh60/cpp_stl_98.html
+++ b/avantes_roh60/cpp_stl_98.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -549,7 +549,7 @@ <h3>avantes_roh60.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/csharp.html b/avantes_roh60/csharp.html
index 55d26e351..a6119e57b 100644
--- a/avantes_roh60/csharp.html
+++ b/avantes_roh60/csharp.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -451,7 +451,7 @@ <h3>AvantesRoh60.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/go.html b/avantes_roh60/go.html
index aee34cdba..3626e45db 100644
--- a/avantes_roh60/go.html
+++ b/avantes_roh60/go.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -441,7 +441,7 @@ <h3>avantes_roh60.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/graphviz.html b/avantes_roh60/graphviz.html
index d548488c3..05a9a6fac 100644
--- a/avantes_roh60/graphviz.html
+++ b/avantes_roh60/graphviz.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -329,7 +329,7 @@ <h3>avantes_roh60.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/index.html b/avantes_roh60/index.html
index c1e4e076f..28fc4e9cd 100644
--- a/avantes_roh60/index.html
+++ b/avantes_roh60/index.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -355,7 +355,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/java.html b/avantes_roh60/java.html
index 2724616ff..c6878c6c7 100644
--- a/avantes_roh60/java.html
+++ b/avantes_roh60/java.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -456,7 +456,7 @@ <h3>AvantesRoh60.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/javascript.html b/avantes_roh60/javascript.html
index 2135325ff..b0f0be5e9 100644
--- a/avantes_roh60/javascript.html
+++ b/avantes_roh60/javascript.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -415,7 +415,7 @@ <h3>AvantesRoh60.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/lua.html b/avantes_roh60/lua.html
index 4cc475df2..f00cc3c15 100644
--- a/avantes_roh60/lua.html
+++ b/avantes_roh60/lua.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -366,7 +366,7 @@ <h3>avantes_roh60.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/nim.html b/avantes_roh60/nim.html
index fff3b884f..cb90e9ef7 100644
--- a/avantes_roh60/nim.html
+++ b/avantes_roh60/nim.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -394,7 +394,7 @@ <h3>avantes_roh60.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/perl.html b/avantes_roh60/perl.html
index 7620cf1b8..e8453b819 100644
--- a/avantes_roh60/perl.html
+++ b/avantes_roh60/perl.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -433,7 +433,7 @@ <h3>AvantesRoh60.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/php.html b/avantes_roh60/php.html
index 20ebcdbc5..dd3d7e111 100644
--- a/avantes_roh60/php.html
+++ b/avantes_roh60/php.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -395,7 +395,7 @@ <h3>AvantesRoh60.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/python.html b/avantes_roh60/python.html
index b634357ce..237b2df1a 100644
--- a/avantes_roh60/python.html
+++ b/avantes_roh60/python.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -409,7 +409,7 @@ <h3>avantes_roh60.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avantes_roh60/ruby.html b/avantes_roh60/ruby.html
index 81a619396..a6d833797 100644
--- a/avantes_roh60/ruby.html
+++ b/avantes_roh60/ruby.html
@@ -105,26 +105,26 @@ <h1>Avantes USB spectrometer ROH file 6.0:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Avantes USB spectrometers are supplied with a Windows binary which
-generates one ROH and one RCM file when the user clicks &quot;Save
-experiment&quot;. In the version of 6.0, the ROH file contains a header
-of 22 four-byte floats, then the spectrum as a float array and a
-footer of 3 floats. The first and last pixel numbers are specified in the
-header and determine the (length+1) of the spectral data. In the tested
-files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this
+                <p><p>Avantes USB spectrometers are supplied with a Windows binary which<br />
+generates one ROH and one RCM file when the user clicks &quot;Save<br />
+experiment&quot;. In the version of 6.0, the ROH file contains a header<br />
+of 22 four-byte floats, then the spectrum as a float array and a<br />
+footer of 3 floats. The first and last pixel numbers are specified in the<br />
+header and determine the (length+1) of the spectral data. In the tested<br />
+files, the length is (2032-211-1)=1820 pixels, but Kaitai determines this<br />
 automatically anyway.</p>
-<p>The wavelength calibration is stored as a polynomial with coefficients
-of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the
-(pixel number + 1), as found out by comparing with the original
-Avantes converted data files. There is no intensity calibration saved,
-but it is recommended to do it in your program - the CCD in the spectrometer
-is so uneven that one should prepare exact pixel-to-pixel calibration curves
+<p>The wavelength calibration is stored as a polynomial with coefficients<br />
+of 'wlintercept', 'wlx1', ... 'wlx4', the argument of which is the<br />
+(pixel number + 1), as found out by comparing with the original<br />
+Avantes converted data files. There is no intensity calibration saved,<br />
+but it is recommended to do it in your program - the CCD in the spectrometer<br />
+is so uneven that one should prepare exact pixel-to-pixel calibration curves<br />
 to get reasonable spectral results.</p>
-<p>The rest of the header floats is not known to the author. Note that the
-newer version of Avantes software has a different format, see also
+<p>The rest of the header floats is not known to the author. Note that the<br />
+newer version of Avantes software has a different format, see also<br />
 <a href="https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab">https://www.mathworks.com/matlabcentral/fileexchange/37103-avantes-to-matlab</a></p>
-<p>The RCM file contains the user-specified comment, so it may be useful
-for automatic conversion of data. You may wish to divide the spectra by
+<p>The RCM file contains the user-specified comment, so it may be useful<br />
+for automatic conversion of data. You may wish to divide the spectra by<br />
 the integration time before comparing them.</p>
 <p>Written and tested by Filip Dominec, 2017-2018</p>
 </p>
@@ -423,7 +423,7 @@ <h3>avantes_roh60.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/cpp_stl_11.html b/avi/cpp_stl_11.html
index 4f6779c79..d03378b8c 100644
--- a/avi/cpp_stl_11.html
+++ b/avi/cpp_stl_11.html
@@ -938,7 +938,7 @@ <h3>avi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/cpp_stl_98.html b/avi/cpp_stl_98.html
index 5a4dd7fe9..5b32b0560 100644
--- a/avi/cpp_stl_98.html
+++ b/avi/cpp_stl_98.html
@@ -1012,7 +1012,7 @@ <h3>avi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/csharp.html b/avi/csharp.html
index 252bbeb1b..4810e3562 100644
--- a/avi/csharp.html
+++ b/avi/csharp.html
@@ -720,7 +720,7 @@ <h3>Avi.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/go.html b/avi/go.html
index d16d7f43f..c6c4daa42 100644
--- a/avi/go.html
+++ b/avi/go.html
@@ -792,7 +792,7 @@ <h3>avi.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/graphviz.html b/avi/graphviz.html
index 2c5d3e179..b20a8f1c2 100644
--- a/avi/graphviz.html
+++ b/avi/graphviz.html
@@ -404,7 +404,7 @@ <h3>avi.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/index.html b/avi/index.html
index 9319d9f60..40bb31a5f 100644
--- a/avi/index.html
+++ b/avi/index.html
@@ -420,7 +420,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/java.html b/avi/java.html
index a4d2b2127..c650e37c0 100644
--- a/avi/java.html
+++ b/avi/java.html
@@ -794,7 +794,7 @@ <h3>Avi.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/javascript.html b/avi/javascript.html
index 69a4703ec..f632f6c2d 100644
--- a/avi/javascript.html
+++ b/avi/javascript.html
@@ -592,7 +592,7 @@ <h3>Avi.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/lua.html b/avi/lua.html
index 28eb26a8a..219071a61 100644
--- a/avi/lua.html
+++ b/avi/lua.html
@@ -501,7 +501,7 @@ <h3>avi.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/nim.html b/avi/nim.html
index ed4e1a346..3c72a3621 100644
--- a/avi/nim.html
+++ b/avi/nim.html
@@ -602,7 +602,7 @@ <h3>avi.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/perl.html b/avi/perl.html
index 7e192e609..1abeac17d 100644
--- a/avi/perl.html
+++ b/avi/perl.html
@@ -833,7 +833,7 @@ <h3>Avi.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/php.html b/avi/php.html
index 2aca8b698..cdee62a7a 100644
--- a/avi/php.html
+++ b/avi/php.html
@@ -586,7 +586,7 @@ <h3>Avi.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/python.html b/avi/python.html
index d92abadfd..8a491e62c 100644
--- a/avi/python.html
+++ b/avi/python.html
@@ -517,7 +517,7 @@ <h3>avi.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/avi/ruby.html b/avi/ruby.html
index 619ae1ac9..8d5a4be9c 100644
--- a/avi/ruby.html
+++ b/avi/ruby.html
@@ -566,7 +566,7 @@ <h3>avi.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/cpp_stl_11.html b/bcd/cpp_stl_11.html
index 1b2e30282..7c896d588 100644
--- a/bcd/cpp_stl_11.html
+++ b/bcd/cpp_stl_11.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -589,7 +589,7 @@ <h3>bcd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/cpp_stl_98.html b/bcd/cpp_stl_98.html
index 75a0e7bfa..163212d81 100644
--- a/bcd/cpp_stl_98.html
+++ b/bcd/cpp_stl_98.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -600,7 +600,7 @@ <h3>bcd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/csharp.html b/bcd/csharp.html
index 8584983f7..64da9d940 100644
--- a/bcd/csharp.html
+++ b/bcd/csharp.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -497,7 +497,7 @@ <h3>Bcd.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/go.html b/bcd/go.html
index e085b940a..d15edc0db 100644
--- a/bcd/go.html
+++ b/bcd/go.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -554,7 +554,7 @@ <h3>bcd.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/graphviz.html b/bcd/graphviz.html
index b4b5e8fbf..70de383bc 100644
--- a/bcd/graphviz.html
+++ b/bcd/graphviz.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -371,7 +371,7 @@ <h3>bcd.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/index.html b/bcd/index.html
index 5c01a78d5..c5bd19bf1 100644
--- a/bcd/index.html
+++ b/bcd/index.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -404,7 +404,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/java.html b/bcd/java.html
index ce77a9080..1b5fc107e 100644
--- a/bcd/java.html
+++ b/bcd/java.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -482,7 +482,7 @@ <h3>Bcd.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/javascript.html b/bcd/javascript.html
index 7f64ed502..3f83ae8b6 100644
--- a/bcd/javascript.html
+++ b/bcd/javascript.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -462,7 +462,7 @@ <h3>Bcd.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/lua.html b/bcd/lua.html
index b07d72655..bb5243e23 100644
--- a/bcd/lua.html
+++ b/bcd/lua.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -407,7 +407,7 @@ <h3>bcd.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/nim.html b/bcd/nim.html
index a203fba69..c11b6febf 100644
--- a/bcd/nim.html
+++ b/bcd/nim.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -424,7 +424,7 @@ <h3>bcd.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/perl.html b/bcd/perl.html
index faa315545..761414bd1 100644
--- a/bcd/perl.html
+++ b/bcd/perl.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -391,7 +391,7 @@ <h3>Bcd.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/php.html b/bcd/php.html
index e85a3f533..c9a13af25 100644
--- a/bcd/php.html
+++ b/bcd/php.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -416,7 +416,7 @@ <h3>Bcd.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/python.html b/bcd/python.html
index 39705f816..382cfb748 100644
--- a/bcd/python.html
+++ b/bcd/python.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -429,7 +429,7 @@ <h3>bcd.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bcd/ruby.html b/bcd/ruby.html
index fce017a92..67fdf35f9 100644
--- a/bcd/ruby.html
+++ b/bcd/ruby.html
@@ -105,25 +105,25 @@ <h1>BCD (Binary Coded Decimals):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer
-numbers in a way that makes human-readable output somewhat
-simpler. In this encoding scheme, every decimal digit is encoded as
-either a single byte (8 bits), or a nibble (half of a byte, 4
-bits). This obviously wastes a lot of bits, but it makes translation
-into human-readable string much easier than traditional
-binary-to-decimal conversion process, which includes lots of
+                <p><p>BCD (Binary Coded Decimals) is a common way to encode integer<br />
+numbers in a way that makes human-readable output somewhat<br />
+simpler. In this encoding scheme, every decimal digit is encoded as<br />
+either a single byte (8 bits), or a nibble (half of a byte, 4<br />
+bits). This obviously wastes a lot of bits, but it makes translation<br />
+into human-readable string much easier than traditional<br />
+binary-to-decimal conversion process, which includes lots of<br />
 divisions by 10.</p>
-<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,
+<p>For example, encoding integer 31337 in 8-digit, 8 bits per digit,<br />
 big endian order of digits BCD format yields</p>
-<pre><code>00 00 00 03 01 03 03 07
-</code></pre>
-<p>Encoding the same integer as 8-digit, 4 bits per digit, little
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">00 00 00 03 01 03 03 07
+</span></code></pre>
+<p>Encoding the same integer as 8-digit, 4 bits per digit, little<br />
 endian order BCD format would yield:</p>
-<pre><code>73 31 30 00
-</code></pre>
-<p>Using this type of encoding in Kaitai Struct is pretty
-straightforward: one calls for this type, specifying desired
-encoding parameters, and gets result using either <code>as_int</code> or
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">73 31 30 00
+</span></code></pre>
+<p>Using this type of encoding in Kaitai Struct is pretty<br />
+straightforward: one calls for this type, specifying desired<br />
+encoding parameters, and gets result using either <code>as_int</code> or<br />
 <code>as_str</code> attributes.</p>
 </p>
             </div>
@@ -439,7 +439,7 @@ <h3>bcd.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/cpp_stl_11.html b/bitcoin_transaction/cpp_stl_11.html
index 0ae86ee2a..9cb83e40d 100644
--- a/bitcoin_transaction/cpp_stl_11.html
+++ b/bitcoin_transaction/cpp_stl_11.html
@@ -825,7 +825,7 @@ <h3>bitcoin_transaction.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/cpp_stl_98.html b/bitcoin_transaction/cpp_stl_98.html
index 75b39be97..c0c223302 100644
--- a/bitcoin_transaction/cpp_stl_98.html
+++ b/bitcoin_transaction/cpp_stl_98.html
@@ -887,7 +887,7 @@ <h3>bitcoin_transaction.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/csharp.html b/bitcoin_transaction/csharp.html
index 1653cc460..145cd5dff 100644
--- a/bitcoin_transaction/csharp.html
+++ b/bitcoin_transaction/csharp.html
@@ -663,7 +663,7 @@ <h3>BitcoinTransaction.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/go.html b/bitcoin_transaction/go.html
index 22a17effb..1d071558d 100644
--- a/bitcoin_transaction/go.html
+++ b/bitcoin_transaction/go.html
@@ -690,7 +690,7 @@ <h3>bitcoin_transaction.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/graphviz.html b/bitcoin_transaction/graphviz.html
index 1d73fe6b4..e0a412e4a 100644
--- a/bitcoin_transaction/graphviz.html
+++ b/bitcoin_transaction/graphviz.html
@@ -340,7 +340,7 @@ <h3>bitcoin_transaction.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/index.html b/bitcoin_transaction/index.html
index 052e97864..4c355d7c3 100644
--- a/bitcoin_transaction/index.html
+++ b/bitcoin_transaction/index.html
@@ -383,7 +383,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/java.html b/bitcoin_transaction/java.html
index ab91b494f..4e2ba42cf 100644
--- a/bitcoin_transaction/java.html
+++ b/bitcoin_transaction/java.html
@@ -692,7 +692,7 @@ <h3>BitcoinTransaction.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/javascript.html b/bitcoin_transaction/javascript.html
index c84f77a44..b17a97cc5 100644
--- a/bitcoin_transaction/javascript.html
+++ b/bitcoin_transaction/javascript.html
@@ -549,7 +549,7 @@ <h3>BitcoinTransaction.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/lua.html b/bitcoin_transaction/lua.html
index 954e8b840..2f7edf7bf 100644
--- a/bitcoin_transaction/lua.html
+++ b/bitcoin_transaction/lua.html
@@ -449,7 +449,7 @@ <h3>bitcoin_transaction.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/nim.html b/bitcoin_transaction/nim.html
index 9739b9537..9a04f97fb 100644
--- a/bitcoin_transaction/nim.html
+++ b/bitcoin_transaction/nim.html
@@ -571,7 +571,7 @@ <h3>bitcoin_transaction.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/perl.html b/bitcoin_transaction/perl.html
index dc8fb272d..f63165b59 100644
--- a/bitcoin_transaction/perl.html
+++ b/bitcoin_transaction/perl.html
@@ -644,7 +644,7 @@ <h3>BitcoinTransaction.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/php.html b/bitcoin_transaction/php.html
index c517b77ab..c3f78cca9 100644
--- a/bitcoin_transaction/php.html
+++ b/bitcoin_transaction/php.html
@@ -532,7 +532,7 @@ <h3>BitcoinTransaction.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/python.html b/bitcoin_transaction/python.html
index ae572e9ac..cbf6c715d 100644
--- a/bitcoin_transaction/python.html
+++ b/bitcoin_transaction/python.html
@@ -413,7 +413,7 @@ <h3>bitcoin_transaction.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bitcoin_transaction/ruby.html b/bitcoin_transaction/ruby.html
index 2a4e7fcf1..ea4a33419 100644
--- a/bitcoin_transaction/ruby.html
+++ b/bitcoin_transaction/ruby.html
@@ -520,7 +520,7 @@ <h3>bitcoin_transaction.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/cpp_stl_11.html b/blender_blend/cpp_stl_11.html
index d0276df6c..d8e908bb2 100644
--- a/blender_blend/cpp_stl_11.html
+++ b/blender_blend/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -994,7 +994,7 @@ <h3>blender_blend.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/cpp_stl_98.html b/blender_blend/cpp_stl_98.html
index a555f8f2e..f105fc226 100644
--- a/blender_blend/cpp_stl_98.html
+++ b/blender_blend/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -1068,7 +1068,7 @@ <h3>blender_blend.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/csharp.html b/blender_blend/csharp.html
index 6f7c3210e..9f56fc8af 100644
--- a/blender_blend/csharp.html
+++ b/blender_blend/csharp.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -796,7 +796,7 @@ <h3>BlenderBlend.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/graphviz.html b/blender_blend/graphviz.html
index a9c83ae57..30b9d2f8c 100644
--- a/blender_blend/graphviz.html
+++ b/blender_blend/graphviz.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -431,7 +431,7 @@ <h3>blender_blend.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/index.html b/blender_blend/index.html
index 653c122e3..ee52aa680 100644
--- a/blender_blend/index.html
+++ b/blender_blend/index.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/java.html b/blender_blend/java.html
index 55a4344c8..74c20dd17 100644
--- a/blender_blend/java.html
+++ b/blender_blend/java.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -797,7 +797,7 @@ <h3>BlenderBlend.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/javascript.html b/blender_blend/javascript.html
index 506b6dc61..ceb22a7d4 100644
--- a/blender_blend/javascript.html
+++ b/blender_blend/javascript.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -641,7 +641,7 @@ <h3>BlenderBlend.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/lua.html b/blender_blend/lua.html
index 143f0959a..771dac8ed 100644
--- a/blender_blend/lua.html
+++ b/blender_blend/lua.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -573,7 +573,7 @@ <h3>blender_blend.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/nim.html b/blender_blend/nim.html
index 9f67b66fd..36a3a3f5b 100644
--- a/blender_blend/nim.html
+++ b/blender_blend/nim.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -648,7 +648,7 @@ <h3>blender_blend.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/perl.html b/blender_blend/perl.html
index beab24c64..58750cd2e 100644
--- a/blender_blend/perl.html
+++ b/blender_blend/perl.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -768,7 +768,7 @@ <h3>BlenderBlend.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/php.html b/blender_blend/php.html
index cf314f151..44c9f04d6 100644
--- a/blender_blend/php.html
+++ b/blender_blend/php.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -642,7 +642,7 @@ <h3>BlenderBlend.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/python.html b/blender_blend/python.html
index 71ed66b13..70bec6311 100644
--- a/blender_blend/python.html
+++ b/blender_blend/python.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -562,7 +562,7 @@ <h3>blender_blend.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/blender_blend/ruby.html b/blender_blend/ruby.html
index 265ebde80..ac7684a8a 100644
--- a/blender_blend/ruby.html
+++ b/blender_blend/ruby.html
@@ -105,16 +105,16 @@ <h1>.blend file format of Blender:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Blender is an open source suite for 3D modelling, sculpting,
-animation, compositing, rendering, preparation of assets for its own
-game engine and exporting to others, etc. <code>.blend</code> is its own binary
-format that saves whole state of suite: current scene, animations,
+                <p><p>Blender is an open source suite for 3D modelling, sculpting,<br />
+animation, compositing, rendering, preparation of assets for its own<br />
+game engine and exporting to others, etc. <code>.blend</code> is its own binary<br />
+format that saves whole state of suite: current scene, animations,<br />
 all software settings, extensions, etc.</p>
-<p>Internally, .blend format is a hybrid semi-self-descriptive
-format. On top level, it contains a simple header and a sequence of
-file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV
-pattern</a>. Pre-last
-block would be a structure with code <code>DNA1</code>, which is a essentially
+<p>Internally, .blend format is a hybrid semi-self-descriptive<br />
+format. On top level, it contains a simple header and a sequence of<br />
+file blocks, which more or less follow typical <a href="https://en.wikipedia.org/wiki/Type-length-value">TLV<br />
+pattern</a>. Pre-last<br />
+block would be a structure with code <code>DNA1</code>, which is a essentially<br />
 a machine-readable schema of all other structures used in this file.</p>
 </p>
             </div>
@@ -601,7 +601,7 @@ <h3>blender_blend.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/cpp_stl_11.html b/bmp/cpp_stl_11.html
index ddc5ad14b..680e128fb 100644
--- a/bmp/cpp_stl_11.html
+++ b/bmp/cpp_stl_11.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -2079,7 +2079,7 @@ <h3>bmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/cpp_stl_98.html b/bmp/cpp_stl_98.html
index 4ee909d73..f761f53d8 100644
--- a/bmp/cpp_stl_98.html
+++ b/bmp/cpp_stl_98.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -2255,7 +2255,7 @@ <h3>bmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/csharp.html b/bmp/csharp.html
index 2539a67cf..b719ac0ed 100644
--- a/bmp/csharp.html
+++ b/bmp/csharp.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1510,7 +1510,7 @@ <h3>Bmp.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/index.html b/bmp/index.html
index c0da652ab..5be904600 100644
--- a/bmp/index.html
+++ b/bmp/index.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -936,7 +936,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/java.html b/bmp/java.html
index 58c7077cc..4f8e5ae64 100644
--- a/bmp/java.html
+++ b/bmp/java.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1516,7 +1516,7 @@ <h3>Bmp.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/javascript.html b/bmp/javascript.html
index 4c2d518ab..16d87592a 100644
--- a/bmp/javascript.html
+++ b/bmp/javascript.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1180,7 +1180,7 @@ <h3>Bmp.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/lua.html b/bmp/lua.html
index 4b2aa297e..3693f22b7 100644
--- a/bmp/lua.html
+++ b/bmp/lua.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1068,7 +1068,7 @@ <h3>bmp.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/nim.html b/bmp/nim.html
index f93d2397e..cd11d846b 100644
--- a/bmp/nim.html
+++ b/bmp/nim.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1282,7 +1282,7 @@ <h3>bmp.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/perl.html b/bmp/perl.html
index 52e2aeb0b..085caddee 100644
--- a/bmp/perl.html
+++ b/bmp/perl.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1479,7 +1479,7 @@ <h3>Bmp.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/php.html b/bmp/php.html
index 712746dfa..f12fd7f24 100644
--- a/bmp/php.html
+++ b/bmp/php.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1235,7 +1235,7 @@ <h3>Bmp.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/python.html b/bmp/python.html
index 383c95692..8b28d8634 100644
--- a/bmp/python.html
+++ b/bmp/python.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -989,7 +989,7 @@ <h3>bmp.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bmp/ruby.html b/bmp/ruby.html
index 6771c3fc7..6ecba02ca 100644
--- a/bmp/ruby.html
+++ b/bmp/ruby.html
@@ -105,39 +105,39 @@ <h1>.bmp file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent
-bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file
-format used to store bitmap digital images, independently of the display
-device (such as a graphics adapter), especially on Microsoft Windows
+                <p><p>The <strong>BMP file format</strong>, also known as <strong>bitmap image file</strong> or <strong>device independent<br />
+bitmap (DIB) file format</strong> or simply a <strong>bitmap</strong>, is a raster graphics image file<br />
+format used to store bitmap digital images, independently of the display<br />
+device (such as a graphics adapter), especially on Microsoft Windows<br />
 and OS/2 operating systems.</p>
-<h2>Samples</h2>
-<p>Great collection of various BMP sample files:
+<h2><a href="#samples" aria-hidden="true" class="anchor" id="samples"></a>Samples</h2>
+<p>Great collection of various BMP sample files:<br />
 <a href="http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html"><strong>BMP Suite Image List</strong></a> (by Jason Summers)</p>
-<p>If only there was such a comprehensive sample suite for every file format! It's like
-a dream for every developer of any binary file format parser. It contains a lot of
-different types and variations of BMP files, even the tricky ones, where it's not clear
+<p>If only there was such a comprehensive sample suite for every file format! It's like<br />
+a dream for every developer of any binary file format parser. It contains a lot of<br />
+different types and variations of BMP files, even the tricky ones, where it's not clear<br />
 from the specification how to deal with them (marked there as &quot;<strong>q</strong>uestionable&quot;).</p>
-<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;
-BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most
+<p>If you make a program which will be able to read all the &quot;<strong>g</strong>ood&quot; and &quot;<strong>q</strong>uestionable&quot;<br />
+BMP files and won't crash on the &quot;<strong>b</strong>ad&quot; ones, it will definitely have one of the most<br />
 extensive support of BMP files in the universe!</p>
-<h2>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
-<p>A beneficial discussion on Adobe forum (archived):
+<h2><a href="#bitmapv2infoheader-and-bitmapv3infoheader" aria-hidden="true" class="anchor" id="bitmapv2infoheader-and-bitmapv3infoheader"></a>BITMAPV2INFOHEADER and BITMAPV3INFOHEADER</h2>
+<p>A beneficial discussion on Adobe forum (archived):<br />
 <a href="https://web.archive.org/web/20150127132443/https://forums.adobe.com/message/3272950"><strong>Invalid BMP Format with Alpha channel</strong></a></p>
-<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't
-any documentation available for this header at the time (and still isn't).
-However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type
-of proprietary header and everything they were writing was taken directly
+<p>In 2010, someone noticed that Photoshop generated BMP with an odd type of header. There wasn't<br />
+any documentation available for this header at the time (and still isn't).<br />
+However, Chris Cox (former Adobe employee) claimed that they hadn't invented any type<br />
+of proprietary header and everything they were writing was taken directly<br />
 from the Microsoft documentation.</p>
-<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.
-Although Microsoft has apparently requested and verified the use of the header,
-the documentation on MSDN has probably got lost and they have probably
+<p>It showed up that the unknown header was called BITMAPV3INFOHEADER.<br />
+Although Microsoft has apparently requested and verified the use of the header,<br />
+the documentation on MSDN has probably got lost and they have probably<br />
 forgotten about this type of header.</p>
-<p>This is the only source I could find about these structures, so we could't rely
-on it so much, but I think supporting them as a read-only format won't harm anything.
+<p>This is the only source I could find about these structures, so we could't rely<br />
+on it so much, but I think supporting them as a read-only format won't harm anything.<br />
 Due to the fact that it isn't documented anywhere else, most applications don't support it.</p>
 <p>All Windows headers at once (including mentioned BITMAPV2INFOHEADER and BITMAPV3INFOHEADER):</p>
 <p><img src="https://web.archive.org/web/20190527043845/https://forums.adobe.com/servlet/JiveServlet/showImage/2-3273299-47801/BMP_Headers.png" alt="Bitmap headers overview" /></p>
-<h2>Specs</h2>
+<h2><a href="#specs" aria-hidden="true" class="anchor" id="specs"></a>Specs</h2>
 <ul>
 <li><a href="https://learn.microsoft.com/en-us/windows/win32/gdi/bitmap-storage">Bitmap Storage (Windows Dev Center)</a>
 <ul>
@@ -1059,7 +1059,7 @@ <h3>bmp.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/cpp_stl_11.html b/broadcom_trx/cpp_stl_11.html
index 1aa4eb8ca..2d8ac815f 100644
--- a/broadcom_trx/cpp_stl_11.html
+++ b/broadcom_trx/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -953,7 +953,7 @@ <h3>broadcom_trx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/cpp_stl_98.html b/broadcom_trx/cpp_stl_98.html
index 6053b9bde..92039c4d2 100644
--- a/broadcom_trx/cpp_stl_98.html
+++ b/broadcom_trx/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -1036,7 +1036,7 @@ <h3>broadcom_trx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/csharp.html b/broadcom_trx/csharp.html
index 793611e28..aa5f9cef3 100644
--- a/broadcom_trx/csharp.html
+++ b/broadcom_trx/csharp.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -699,7 +699,7 @@ <h3>BroadcomTrx.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/go.html b/broadcom_trx/go.html
index 618bc9d47..5e9e20617 100644
--- a/broadcom_trx/go.html
+++ b/broadcom_trx/go.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -750,7 +750,7 @@ <h3>broadcom_trx.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/index.html b/broadcom_trx/index.html
index 8a054f873..492781c9c 100644
--- a/broadcom_trx/index.html
+++ b/broadcom_trx/index.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -387,7 +387,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/java.html b/broadcom_trx/java.html
index b8db3686e..6412e0c33 100644
--- a/broadcom_trx/java.html
+++ b/broadcom_trx/java.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -698,7 +698,7 @@ <h3>BroadcomTrx.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/javascript.html b/broadcom_trx/javascript.html
index db1126bc8..ac67c6244 100644
--- a/broadcom_trx/javascript.html
+++ b/broadcom_trx/javascript.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -560,7 +560,7 @@ <h3>BroadcomTrx.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/lua.html b/broadcom_trx/lua.html
index 5f2e83daf..97286edd5 100644
--- a/broadcom_trx/lua.html
+++ b/broadcom_trx/lua.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -509,7 +509,7 @@ <h3>broadcom_trx.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/nim.html b/broadcom_trx/nim.html
index 179133862..9c9af62c9 100644
--- a/broadcom_trx/nim.html
+++ b/broadcom_trx/nim.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -574,7 +574,7 @@ <h3>broadcom_trx.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/perl.html b/broadcom_trx/perl.html
index 4674b548e..c2561cc58 100644
--- a/broadcom_trx/perl.html
+++ b/broadcom_trx/perl.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -717,7 +717,7 @@ <h3>BroadcomTrx.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/php.html b/broadcom_trx/php.html
index aa2ba5df1..900fadd58 100644
--- a/broadcom_trx/php.html
+++ b/broadcom_trx/php.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -530,7 +530,7 @@ <h3>BroadcomTrx.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/python.html b/broadcom_trx/python.html
index dcbe01ac9..6c6c54389 100644
--- a/broadcom_trx/python.html
+++ b/broadcom_trx/python.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -512,7 +512,7 @@ <h3>broadcom_trx.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/broadcom_trx/ruby.html b/broadcom_trx/ruby.html
index d37deab2c..881ace9bc 100644
--- a/broadcom_trx/ruby.html
+++ b/broadcom_trx/ruby.html
@@ -105,11 +105,11 @@ <h1>Broadcom devices .trx firmware packaging:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trx file format is widely used for distribution of firmware
+                <p><p>.trx file format is widely used for distribution of firmware<br />
 updates for Broadcom devices. The most well-known are ASUS routers.</p>
-<p>Fundamentally, it includes a footer which acts as a safeguard
-against installing a firmware package on a wrong hardware model or
-version, and a header which list numerous partitions packaged inside
+<p>Fundamentally, it includes a footer which acts as a safeguard<br />
+against installing a firmware package on a wrong hardware model or<br />
+version, and a header which list numerous partitions packaged inside<br />
 a single .trx file.</p>
 <p>trx files not necessarily contain all these headers.</p>
 </p>
@@ -521,7 +521,7 @@ <h3>broadcom_trx.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/csharp.html b/bson/csharp.html
index 7525c83d9..70af6e933 100644
--- a/bson/csharp.html
+++ b/bson/csharp.html
@@ -927,7 +927,7 @@ <h3>Bson.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/go.html b/bson/go.html
index b460483e6..ff2f49ee8 100644
--- a/bson/go.html
+++ b/bson/go.html
@@ -1000,7 +1000,7 @@ <h3>bson.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/graphviz.html b/bson/graphviz.html
index be9137ce4..48e35cf92 100644
--- a/bson/graphviz.html
+++ b/bson/graphviz.html
@@ -482,7 +482,7 @@ <h3>bson.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/index.html b/bson/index.html
index b6878b13e..c2be840b0 100644
--- a/bson/index.html
+++ b/bson/index.html
@@ -455,7 +455,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/java.html b/bson/java.html
index bd4585e71..e29c08b69 100644
--- a/bson/java.html
+++ b/bson/java.html
@@ -1026,7 +1026,7 @@ <h3>Bson.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/javascript.html b/bson/javascript.html
index 413b878a9..096573c81 100644
--- a/bson/javascript.html
+++ b/bson/javascript.html
@@ -755,7 +755,7 @@ <h3>Bson.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/lua.html b/bson/lua.html
index 129ccd8b0..7aa7f2ee1 100644
--- a/bson/lua.html
+++ b/bson/lua.html
@@ -626,7 +626,7 @@ <h3>bson.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/nim.html b/bson/nim.html
index a18af04b6..2b61ec168 100644
--- a/bson/nim.html
+++ b/bson/nim.html
@@ -761,7 +761,7 @@ <h3>bson.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/perl.html b/bson/perl.html
index 8dc1375e2..4a9c3fd8a 100644
--- a/bson/perl.html
+++ b/bson/perl.html
@@ -1057,7 +1057,7 @@ <h3>Bson.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/php.html b/bson/php.html
index c3cd7c76b..0cec4d59a 100644
--- a/bson/php.html
+++ b/bson/php.html
@@ -722,7 +722,7 @@ <h3>Bson.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/python.html b/bson/python.html
index 27b42f89a..e3dc380bf 100644
--- a/bson/python.html
+++ b/bson/python.html
@@ -607,7 +607,7 @@ <h3>bson.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bson/ruby.html b/bson/ruby.html
index c020f5262..3b1fbe747 100644
--- a/bson/ruby.html
+++ b/bson/ruby.html
@@ -669,7 +669,7 @@ <h3>bson.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/csharp.html b/btrfs_stream/csharp.html
index c3645cc62..a5473b635 100644
--- a/btrfs_stream/csharp.html
+++ b/btrfs_stream/csharp.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -750,7 +750,7 @@ <h3>BtrfsStream.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/go.html b/btrfs_stream/go.html
index 774e1738d..cf8275557 100644
--- a/btrfs_stream/go.html
+++ b/btrfs_stream/go.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -843,7 +843,7 @@ <h3>btrfs_stream.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/graphviz.html b/btrfs_stream/graphviz.html
index 18c763a65..2bd297190 100644
--- a/btrfs_stream/graphviz.html
+++ b/btrfs_stream/graphviz.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -393,7 +393,7 @@ <h3>btrfs_stream.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/index.html b/btrfs_stream/index.html
index c1cb8ca8b..9719e8c39 100644
--- a/btrfs_stream/index.html
+++ b/btrfs_stream/index.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -423,7 +423,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/java.html b/btrfs_stream/java.html
index 600ebad78..1d928c531 100644
--- a/btrfs_stream/java.html
+++ b/btrfs_stream/java.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -819,7 +819,7 @@ <h3>BtrfsStream.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/javascript.html b/btrfs_stream/javascript.html
index 8d2e295cc..8544f3cec 100644
--- a/btrfs_stream/javascript.html
+++ b/btrfs_stream/javascript.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -679,7 +679,7 @@ <h3>BtrfsStream.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/lua.html b/btrfs_stream/lua.html
index aa86ae519..dd368cea8 100644
--- a/btrfs_stream/lua.html
+++ b/btrfs_stream/lua.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -552,7 +552,7 @@ <h3>btrfs_stream.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/nim.html b/btrfs_stream/nim.html
index 221add24d..9d2758104 100644
--- a/btrfs_stream/nim.html
+++ b/btrfs_stream/nim.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -629,7 +629,7 @@ <h3>btrfs_stream.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/perl.html b/btrfs_stream/perl.html
index aadf9a5ba..943d04eda 100644
--- a/btrfs_stream/perl.html
+++ b/btrfs_stream/perl.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -791,7 +791,7 @@ <h3>BtrfsStream.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/php.html b/btrfs_stream/php.html
index 7bfc8bb0b..a2a0efa6c 100644
--- a/btrfs_stream/php.html
+++ b/btrfs_stream/php.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -603,7 +603,7 @@ <h3>BtrfsStream.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/python.html b/btrfs_stream/python.html
index fa60a1099..9f94592be 100644
--- a/btrfs_stream/python.html
+++ b/btrfs_stream/python.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -566,7 +566,7 @@ <h3>btrfs_stream.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/btrfs_stream/ruby.html b/btrfs_stream/ruby.html
index 78b5dcc5f..65b65777a 100644
--- a/btrfs_stream/ruby.html
+++ b/btrfs_stream/ruby.html
@@ -105,14 +105,14 @@ <h1>btrfs_stream:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy
-administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and
-integral multi-device spanning in Linux file systems.
-Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by
-using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a
-different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required
-for converting one subvolume into another.
-This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.
+                <p><p>Btrfs is a copy on write file system based on B-trees focusing on fault tolerance, repair and easy<br />
+administration. Btrfs is intended to address the lack of pooling, snapshots, checksums, and<br />
+integral multi-device spanning in Linux file systems.<br />
+Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them by<br />
+using the <code>btrfs send</code> command that can be replayed later by using <code>btrfs receive</code>, possibly on a<br />
+different Btrfs file system. The <code>btrfs send</code> command creates a set of data modifications required<br />
+for converting one subvolume into another.<br />
+This spec can be used to disassemble the binary diff created by the <code>btrfs send</code> command.<br />
 If you want a text representation you may want to checkout <code>btrfs receive --dump</code> instead.</p>
 </p>
             </div>
@@ -590,7 +590,7 @@ <h3>btrfs_stream.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/cpp_stl_11.html b/bytes_with_io/cpp_stl_11.html
index c0bbc4256..1323ccef8 100644
--- a/bytes_with_io/cpp_stl_11.html
+++ b/bytes_with_io/cpp_stl_11.html
@@ -404,7 +404,7 @@ <h3>bytes_with_io.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/cpp_stl_98.html b/bytes_with_io/cpp_stl_98.html
index ea0bd3413..396bbbc5f 100644
--- a/bytes_with_io/cpp_stl_98.html
+++ b/bytes_with_io/cpp_stl_98.html
@@ -412,7 +412,7 @@ <h3>bytes_with_io.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/csharp.html b/bytes_with_io/csharp.html
index d84fb1546..e0750bef8 100644
--- a/bytes_with_io/csharp.html
+++ b/bytes_with_io/csharp.html
@@ -327,7 +327,7 @@ <h3>BytesWithIo.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/go.html b/bytes_with_io/go.html
index cf21ec202..0b7525766 100644
--- a/bytes_with_io/go.html
+++ b/bytes_with_io/go.html
@@ -282,7 +282,7 @@ <h3>bytes_with_io.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/graphviz.html b/bytes_with_io/graphviz.html
index de4b6b782..12f4597cf 100644
--- a/bytes_with_io/graphviz.html
+++ b/bytes_with_io/graphviz.html
@@ -259,7 +259,7 @@ <h3>bytes_with_io.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/index.html b/bytes_with_io/index.html
index a1cfb087a..3f5abaf8d 100644
--- a/bytes_with_io/index.html
+++ b/bytes_with_io/index.html
@@ -243,7 +243,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/java.html b/bytes_with_io/java.html
index 6747090d0..ddb533286 100644
--- a/bytes_with_io/java.html
+++ b/bytes_with_io/java.html
@@ -334,7 +334,7 @@ <h3>BytesWithIo.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/javascript.html b/bytes_with_io/javascript.html
index 9ea1c0494..d3f290c6f 100644
--- a/bytes_with_io/javascript.html
+++ b/bytes_with_io/javascript.html
@@ -320,7 +320,7 @@ <h3>BytesWithIo.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/lua.html b/bytes_with_io/lua.html
index ccd9dbe67..5ce0bb086 100644
--- a/bytes_with_io/lua.html
+++ b/bytes_with_io/lua.html
@@ -270,7 +270,7 @@ <h3>bytes_with_io.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/nim.html b/bytes_with_io/nim.html
index 42ab87d72..6e848113a 100644
--- a/bytes_with_io/nim.html
+++ b/bytes_with_io/nim.html
@@ -279,7 +279,7 @@ <h3>bytes_with_io.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/perl.html b/bytes_with_io/perl.html
index 0bc30819a..988624d33 100644
--- a/bytes_with_io/perl.html
+++ b/bytes_with_io/perl.html
@@ -291,7 +291,7 @@ <h3>BytesWithIo.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/php.html b/bytes_with_io/php.html
index ab3a61311..5d84f10d7 100644
--- a/bytes_with_io/php.html
+++ b/bytes_with_io/php.html
@@ -271,7 +271,7 @@ <h3>BytesWithIo.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/python.html b/bytes_with_io/python.html
index 6b90f4535..4b8373eeb 100644
--- a/bytes_with_io/python.html
+++ b/bytes_with_io/python.html
@@ -310,7 +310,7 @@ <h3>bytes_with_io.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/bytes_with_io/ruby.html b/bytes_with_io/ruby.html
index b766882de..e6c73c030 100644
--- a/bytes_with_io/ruby.html
+++ b/bytes_with_io/ruby.html
@@ -314,7 +314,7 @@ <h3>bytes_with_io.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/cpp_stl_11.html b/chrome_pak/cpp_stl_11.html
index 408cd2d89..47aa80b97 100644
--- a/chrome_pak/cpp_stl_11.html
+++ b/chrome_pak/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -755,7 +755,7 @@ <h3>chrome_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/cpp_stl_98.html b/chrome_pak/cpp_stl_98.html
index f4df04fd8..108f27967 100644
--- a/chrome_pak/cpp_stl_98.html
+++ b/chrome_pak/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -796,7 +796,7 @@ <h3>chrome_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/csharp.html b/chrome_pak/csharp.html
index 1cdd61293..52c81dcf9 100644
--- a/chrome_pak/csharp.html
+++ b/chrome_pak/csharp.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -575,7 +575,7 @@ <h3>ChromePak.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/go.html b/chrome_pak/go.html
index d18d601c2..4769847e7 100644
--- a/chrome_pak/go.html
+++ b/chrome_pak/go.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -584,7 +584,7 @@ <h3>chrome_pak.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/graphviz.html b/chrome_pak/graphviz.html
index 1a9164ee1..86c75b45e 100644
--- a/chrome_pak/graphviz.html
+++ b/chrome_pak/graphviz.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -341,7 +341,7 @@ <h3>chrome_pak.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/index.html b/chrome_pak/index.html
index 2f6b36ff8..977c8d365 100644
--- a/chrome_pak/index.html
+++ b/chrome_pak/index.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -353,7 +353,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/java.html b/chrome_pak/java.html
index a4244aae9..2a2087ca8 100644
--- a/chrome_pak/java.html
+++ b/chrome_pak/java.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -569,7 +569,7 @@ <h3>ChromePak.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/javascript.html b/chrome_pak/javascript.html
index 1ebe7d00d..b04b15067 100644
--- a/chrome_pak/javascript.html
+++ b/chrome_pak/javascript.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -487,7 +487,7 @@ <h3>ChromePak.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/lua.html b/chrome_pak/lua.html
index 59acb80c4..fa85a5788 100644
--- a/chrome_pak/lua.html
+++ b/chrome_pak/lua.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -433,7 +433,7 @@ <h3>chrome_pak.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/nim.html b/chrome_pak/nim.html
index caeead1dc..f95db548c 100644
--- a/chrome_pak/nim.html
+++ b/chrome_pak/nim.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -474,7 +474,7 @@ <h3>chrome_pak.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/perl.html b/chrome_pak/perl.html
index 2c5eab7f5..0b0d7bdd2 100644
--- a/chrome_pak/perl.html
+++ b/chrome_pak/perl.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -535,7 +535,7 @@ <h3>ChromePak.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/php.html b/chrome_pak/php.html
index 1a7739bf8..90ce8aa47 100644
--- a/chrome_pak/php.html
+++ b/chrome_pak/php.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -464,7 +464,7 @@ <h3>ChromePak.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/python.html b/chrome_pak/python.html
index 0601208ec..8b2493de0 100644
--- a/chrome_pak/python.html
+++ b/chrome_pak/python.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -443,7 +443,7 @@ <h3>chrome_pak.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/chrome_pak/ruby.html b/chrome_pak/ruby.html
index a0f02ca44..2cbc07fcd 100644
--- a/chrome_pak/ruby.html
+++ b/chrome_pak/ruby.html
@@ -105,7 +105,7 @@ <h1>Chrome PAK serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Format mostly used by Google Chrome and various Android apps to store
+                <p><p>Format mostly used by Google Chrome and various Android apps to store<br />
 resources such as translated strings, help messages and images.</p>
 </p>
             </div>
@@ -457,7 +457,7 @@ <h3>chrome_pak.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/cpp_stl_11.html b/code_6502/cpp_stl_11.html
index 64fc09aea..e1cdf1fc8 100644
--- a/code_6502/cpp_stl_11.html
+++ b/code_6502/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1258,7 +1258,7 @@ <h3>code_6502.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/cpp_stl_98.html b/code_6502/cpp_stl_98.html
index 4dd34ce47..1e4682c27 100644
--- a/code_6502/cpp_stl_98.html
+++ b/code_6502/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1278,7 +1278,7 @@ <h3>code_6502.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/csharp.html b/code_6502/csharp.html
index 8592cc912..48260c9ba 100644
--- a/code_6502/csharp.html
+++ b/code_6502/csharp.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1031,7 +1031,7 @@ <h3>Code6502.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/go.html b/code_6502/go.html
index 015dff063..98f073df3 100644
--- a/code_6502/go.html
+++ b/code_6502/go.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1230,7 +1230,7 @@ <h3>code_6502.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/graphviz.html b/code_6502/graphviz.html
index 3044cacf0..d6f7b36a7 100644
--- a/code_6502/graphviz.html
+++ b/code_6502/graphviz.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -303,7 +303,7 @@ <h3>code_6502.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/index.html b/code_6502/index.html
index a1ecacf7f..602ee89bb 100644
--- a/code_6502/index.html
+++ b/code_6502/index.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -560,7 +560,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/java.html b/code_6502/java.html
index 7a7fdac76..896f0ad5b 100644
--- a/code_6502/java.html
+++ b/code_6502/java.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1060,7 +1060,7 @@ <h3>Code6502.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/javascript.html b/code_6502/javascript.html
index 488f23113..fb51865db 100644
--- a/code_6502/javascript.html
+++ b/code_6502/javascript.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -1040,7 +1040,7 @@ <h3>Code6502.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/lua.html b/code_6502/lua.html
index b568987b5..786b35996 100644
--- a/code_6502/lua.html
+++ b/code_6502/lua.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>code_6502.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/nim.html b/code_6502/nim.html
index e97c84c6f..2dd2538c8 100644
--- a/code_6502/nim.html
+++ b/code_6502/nim.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -848,7 +848,7 @@ <h3>code_6502.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/perl.html b/code_6502/perl.html
index e477e8e8f..6b88448cc 100644
--- a/code_6502/perl.html
+++ b/code_6502/perl.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -883,7 +883,7 @@ <h3>Code6502.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/php.html b/code_6502/php.html
index 49c724e9f..5e6aa0e10 100644
--- a/code_6502/php.html
+++ b/code_6502/php.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -843,7 +843,7 @@ <h3>Code6502.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/python.html b/code_6502/python.html
index 65974a8ae..a82955c07 100644
--- a/code_6502/python.html
+++ b/code_6502/python.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -754,7 +754,7 @@ <h3>code_6502.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/code_6502/ruby.html b/code_6502/ruby.html
index ca89ff807..efe07f8e4 100644
--- a/code_6502/ruby.html
+++ b/code_6502/ruby.html
@@ -105,9 +105,9 @@ <h1>code_6502:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine
-code into individual operations. Each operation includes an opcode
-and, optionally, an argument. Register arguments are part of the
+                <p><p>This spec can be used to disassemble raw stream of 6502 CPU machine<br />
+code into individual operations. Each operation includes an opcode<br />
+and, optionally, an argument. Register arguments are part of the<br />
 <code>opcode</code> enum.</p>
 </p>
             </div>
@@ -760,7 +760,7 @@ <h3>code_6502.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/cpp_stl_11.html b/compressed_resource/cpp_stl_11.html
index dc7951c25..d56b759ba 100644
--- a/compressed_resource/cpp_stl_11.html
+++ b/compressed_resource/cpp_stl_11.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -878,7 +878,7 @@ <h3>compressed_resource.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/cpp_stl_98.html b/compressed_resource/cpp_stl_98.html
index bfaf2d361..fbb862423 100644
--- a/compressed_resource/cpp_stl_98.html
+++ b/compressed_resource/cpp_stl_98.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -931,7 +931,7 @@ <h3>compressed_resource.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/csharp.html b/compressed_resource/csharp.html
index aff6374a1..b3765bdf4 100644
--- a/compressed_resource/csharp.html
+++ b/compressed_resource/csharp.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -709,7 +709,7 @@ <h3>CompressedResource.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/go.html b/compressed_resource/go.html
index f98641239..36e8cea39 100644
--- a/compressed_resource/go.html
+++ b/compressed_resource/go.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -701,7 +701,7 @@ <h3>compressed_resource.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/index.html b/compressed_resource/index.html
index 2f48abe83..6afdc6b2a 100644
--- a/compressed_resource/index.html
+++ b/compressed_resource/index.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -436,7 +436,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/java.html b/compressed_resource/java.html
index 820c1f287..61d3ec7da 100644
--- a/compressed_resource/java.html
+++ b/compressed_resource/java.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -706,7 +706,7 @@ <h3>CompressedResource.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/javascript.html b/compressed_resource/javascript.html
index d191a3128..76bb47389 100644
--- a/compressed_resource/javascript.html
+++ b/compressed_resource/javascript.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -612,7 +612,7 @@ <h3>CompressedResource.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/lua.html b/compressed_resource/lua.html
index 4b02b1c2d..3f811b5bc 100644
--- a/compressed_resource/lua.html
+++ b/compressed_resource/lua.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -522,7 +522,7 @@ <h3>compressed_resource.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/nim.html b/compressed_resource/nim.html
index 27f592412..528f37c91 100644
--- a/compressed_resource/nim.html
+++ b/compressed_resource/nim.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -627,7 +627,7 @@ <h3>compressed_resource.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/perl.html b/compressed_resource/perl.html
index fbc134244..9c7256a24 100644
--- a/compressed_resource/perl.html
+++ b/compressed_resource/perl.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -570,7 +570,7 @@ <h3>CompressedResource.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/php.html b/compressed_resource/php.html
index cfc31ab8c..e370e3cd5 100644
--- a/compressed_resource/php.html
+++ b/compressed_resource/php.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -581,7 +581,7 @@ <h3>CompressedResource.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/python.html b/compressed_resource/python.html
index 078530713..d12c86b59 100644
--- a/compressed_resource/python.html
+++ b/compressed_resource/python.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -480,7 +480,7 @@ <h3>compressed_resource.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/compressed_resource/ruby.html b/compressed_resource/ruby.html
index fca4a3d82..07c725b48 100644
--- a/compressed_resource/ruby.html
+++ b/compressed_resource/ruby.html
@@ -105,21 +105,21 @@ <h1>Compressed Macintosh resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed Macintosh resource data,
+                <p><p>Compressed Macintosh resource data,<br />
 as stored in resources with the &quot;compressed&quot; attribute.</p>
-<p>Resource decompression is not documented by Apple.
-It is mostly used internally in System 7,
-some of Apple's own applications (such as ResEdit),
-and also by some third-party applications.
-Later versions of Classic Mac OS make less use of resource compression,
-but still support it fully for backwards compatibility.
+<p>Resource decompression is not documented by Apple.<br />
+It is mostly used internally in System 7,<br />
+some of Apple's own applications (such as ResEdit),<br />
+and also by some third-party applications.<br />
+Later versions of Classic Mac OS make less use of resource compression,<br />
+but still support it fully for backwards compatibility.<br />
 Carbon in Mac OS X no longer supports resource compression in any way.</p>
-<p>The data of all compressed resources starts with a common header,
-followed by the compressed data.
-The data is decompressed using code in a <code>'dcmp'</code> resource.
-Some decompressors used by Apple are included in the System file,
-but applications can also include custom decompressors.
-The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,
+<p>The data of all compressed resources starts with a common header,<br />
+followed by the compressed data.<br />
+The data is decompressed using code in a <code>'dcmp'</code> resource.<br />
+Some decompressors used by Apple are included in the System file,<br />
+but applications can also include custom decompressors.<br />
+The header of the compressed data indicates the ID of the <code>'dcmp'</code> resource used to decompress the data,<br />
 along with some parameters for the decompressor.</p>
 </p>
             </div>
@@ -566,7 +566,7 @@ <h3>compressed_resource.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/cpp_stl_11.html b/cpio_old_le/cpp_stl_11.html
index a335ae33e..33cf1080a 100644
--- a/cpio_old_le/cpp_stl_11.html
+++ b/cpio_old_le/cpp_stl_11.html
@@ -680,7 +680,7 @@ <h3>cpio_old_le.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/cpp_stl_98.html b/cpio_old_le/cpp_stl_98.html
index 02d2046d7..b3a1fbb06 100644
--- a/cpio_old_le/cpp_stl_98.html
+++ b/cpio_old_le/cpp_stl_98.html
@@ -721,7 +721,7 @@ <h3>cpio_old_le.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/csharp.html b/cpio_old_le/csharp.html
index 55c6a3ea6..84c096443 100644
--- a/cpio_old_le/csharp.html
+++ b/cpio_old_le/csharp.html
@@ -515,7 +515,7 @@ <h3>CpioOldLe.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/go.html b/cpio_old_le/go.html
index f6b6645ac..48de5044d 100644
--- a/cpio_old_le/go.html
+++ b/cpio_old_le/go.html
@@ -545,7 +545,7 @@ <h3>cpio_old_le.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/graphviz.html b/cpio_old_le/graphviz.html
index 7a46c69d8..ce1f4464e 100644
--- a/cpio_old_le/graphviz.html
+++ b/cpio_old_le/graphviz.html
@@ -346,7 +346,7 @@ <h3>cpio_old_le.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/index.html b/cpio_old_le/index.html
index 27d8a359d..f9f4e9b71 100644
--- a/cpio_old_le/index.html
+++ b/cpio_old_le/index.html
@@ -332,7 +332,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/java.html b/cpio_old_le/java.html
index 93e9fcbd1..92ce3fd44 100644
--- a/cpio_old_le/java.html
+++ b/cpio_old_le/java.html
@@ -529,7 +529,7 @@ <h3>CpioOldLe.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/javascript.html b/cpio_old_le/javascript.html
index e07e8e080..1131d92db 100644
--- a/cpio_old_le/javascript.html
+++ b/cpio_old_le/javascript.html
@@ -435,7 +435,7 @@ <h3>CpioOldLe.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/lua.html b/cpio_old_le/lua.html
index 4382f9821..f44b0a22b 100644
--- a/cpio_old_le/lua.html
+++ b/cpio_old_le/lua.html
@@ -387,7 +387,7 @@ <h3>cpio_old_le.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/nim.html b/cpio_old_le/nim.html
index 6bf981eec..d8fe9160f 100644
--- a/cpio_old_le/nim.html
+++ b/cpio_old_le/nim.html
@@ -423,7 +423,7 @@ <h3>cpio_old_le.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/perl.html b/cpio_old_le/perl.html
index 039edfe3a..0ae2f0db7 100644
--- a/cpio_old_le/perl.html
+++ b/cpio_old_le/perl.html
@@ -553,7 +553,7 @@ <h3>CpioOldLe.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/php.html b/cpio_old_le/php.html
index 1e05fad24..388e01553 100644
--- a/cpio_old_le/php.html
+++ b/cpio_old_le/php.html
@@ -419,7 +419,7 @@ <h3>CpioOldLe.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/python.html b/cpio_old_le/python.html
index 8927dc812..b2e0c1d68 100644
--- a/cpio_old_le/python.html
+++ b/cpio_old_le/python.html
@@ -414,7 +414,7 @@ <h3>cpio_old_le.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cpio_old_le/ruby.html b/cpio_old_le/ruby.html
index 9bd2601e6..fc671e49d 100644
--- a/cpio_old_le/ruby.html
+++ b/cpio_old_le/ruby.html
@@ -428,7 +428,7 @@ <h3>cpio_old_le.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/cpp_stl_11.html b/cramfs/cpp_stl_11.html
index c3ada96eb..a2a4eda9b 100644
--- a/cramfs/cpp_stl_11.html
+++ b/cramfs/cpp_stl_11.html
@@ -1036,7 +1036,7 @@ <h3>cramfs.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/cpp_stl_98.html b/cramfs/cpp_stl_98.html
index c21389cce..78b63b2f4 100644
--- a/cramfs/cpp_stl_98.html
+++ b/cramfs/cpp_stl_98.html
@@ -1104,7 +1104,7 @@ <h3>cramfs.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/csharp.html b/cramfs/csharp.html
index 61909a412..f489215d8 100644
--- a/cramfs/csharp.html
+++ b/cramfs/csharp.html
@@ -807,7 +807,7 @@ <h3>Cramfs.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/go.html b/cramfs/go.html
index f1f870c9a..d27456b1f 100644
--- a/cramfs/go.html
+++ b/cramfs/go.html
@@ -826,7 +826,7 @@ <h3>cramfs.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/graphviz.html b/cramfs/graphviz.html
index dd137dd71..c089e3b7d 100644
--- a/cramfs/graphviz.html
+++ b/cramfs/graphviz.html
@@ -445,7 +445,7 @@ <h3>cramfs.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/index.html b/cramfs/index.html
index e41126fb8..c8040f505 100644
--- a/cramfs/index.html
+++ b/cramfs/index.html
@@ -402,7 +402,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/java.html b/cramfs/java.html
index 0c93573a9..95bf105b1 100644
--- a/cramfs/java.html
+++ b/cramfs/java.html
@@ -738,7 +738,7 @@ <h3>Cramfs.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/javascript.html b/cramfs/javascript.html
index 4adddd113..d71601cb8 100644
--- a/cramfs/javascript.html
+++ b/cramfs/javascript.html
@@ -617,7 +617,7 @@ <h3>Cramfs.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/lua.html b/cramfs/lua.html
index 6bc88224c..ca6a59b29 100644
--- a/cramfs/lua.html
+++ b/cramfs/lua.html
@@ -596,7 +596,7 @@ <h3>cramfs.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/nim.html b/cramfs/nim.html
index b34b868ba..7c4648ee6 100644
--- a/cramfs/nim.html
+++ b/cramfs/nim.html
@@ -656,7 +656,7 @@ <h3>cramfs.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/perl.html b/cramfs/perl.html
index 0b4212f2e..5fd926b92 100644
--- a/cramfs/perl.html
+++ b/cramfs/perl.html
@@ -757,7 +757,7 @@ <h3>Cramfs.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/php.html b/cramfs/php.html
index 52ad055c6..cbd76e84e 100644
--- a/cramfs/php.html
+++ b/cramfs/php.html
@@ -577,7 +577,7 @@ <h3>Cramfs.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/python.html b/cramfs/python.html
index cbbc44c6c..15314373e 100644
--- a/cramfs/python.html
+++ b/cramfs/python.html
@@ -583,7 +583,7 @@ <h3>cramfs.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/cramfs/ruby.html b/cramfs/ruby.html
index 53f6d0ae6..9a0aa8f50 100644
--- a/cramfs/ruby.html
+++ b/cramfs/ruby.html
@@ -549,7 +549,7 @@ <h3>cramfs.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/cpp_stl_11.html b/creative_voice_file/cpp_stl_11.html
index 247a8daf1..da2385590 100644
--- a/creative_voice_file/cpp_stl_11.html
+++ b/creative_voice_file/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -1118,7 +1118,7 @@ <h3>creative_voice_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/cpp_stl_98.html b/creative_voice_file/cpp_stl_98.html
index f73c31730..f8fd8c865 100644
--- a/creative_voice_file/cpp_stl_98.html
+++ b/creative_voice_file/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -1180,7 +1180,7 @@ <h3>creative_voice_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/csharp.html b/creative_voice_file/csharp.html
index 6b6d8d262..9cc05281c 100644
--- a/creative_voice_file/csharp.html
+++ b/creative_voice_file/csharp.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -851,7 +851,7 @@ <h3>CreativeVoiceFile.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/go.html b/creative_voice_file/go.html
index ff9c03cd9..39f3e9161 100644
--- a/creative_voice_file/go.html
+++ b/creative_voice_file/go.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -914,7 +914,7 @@ <h3>creative_voice_file.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/graphviz.html b/creative_voice_file/graphviz.html
index 62ac835f1..58ccd1d67 100644
--- a/creative_voice_file/graphviz.html
+++ b/creative_voice_file/graphviz.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -430,7 +430,7 @@ <h3>creative_voice_file.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/index.html b/creative_voice_file/index.html
index 222c27001..031e8d785 100644
--- a/creative_voice_file/index.html
+++ b/creative_voice_file/index.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -445,7 +445,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/java.html b/creative_voice_file/java.html
index 3979ca2b9..e451886b2 100644
--- a/creative_voice_file/java.html
+++ b/creative_voice_file/java.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -883,7 +883,7 @@ <h3>CreativeVoiceFile.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/javascript.html b/creative_voice_file/javascript.html
index b5b14d069..1bf3f7f2c 100644
--- a/creative_voice_file/javascript.html
+++ b/creative_voice_file/javascript.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -715,7 +715,7 @@ <h3>CreativeVoiceFile.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/lua.html b/creative_voice_file/lua.html
index 17cec2065..b7299632c 100644
--- a/creative_voice_file/lua.html
+++ b/creative_voice_file/lua.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -605,7 +605,7 @@ <h3>creative_voice_file.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/nim.html b/creative_voice_file/nim.html
index a6e6788a4..b917bff0e 100644
--- a/creative_voice_file/nim.html
+++ b/creative_voice_file/nim.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -722,7 +722,7 @@ <h3>creative_voice_file.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/perl.html b/creative_voice_file/perl.html
index c2b7937ce..3462463a1 100644
--- a/creative_voice_file/perl.html
+++ b/creative_voice_file/perl.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -809,7 +809,7 @@ <h3>CreativeVoiceFile.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/php.html b/creative_voice_file/php.html
index 913cb0dcc..ebd0c226f 100644
--- a/creative_voice_file/php.html
+++ b/creative_voice_file/php.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -655,7 +655,7 @@ <h3>CreativeVoiceFile.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/python.html b/creative_voice_file/python.html
index 17921d6ef..4d08005f7 100644
--- a/creative_voice_file/python.html
+++ b/creative_voice_file/python.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -596,7 +596,7 @@ <h3>creative_voice_file.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/creative_voice_file/ruby.html b/creative_voice_file/ruby.html
index 724bdd4a7..483f28d44 100644
--- a/creative_voice_file/ruby.html
+++ b/creative_voice_file/ruby.html
@@ -105,14 +105,14 @@ <h1>Creative Voice File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Creative Voice File is a container file format for digital audio
-wave data. Initial revisions were able to support only unsigned
-8-bit PCM and ADPCM data, later versions were revised to add support
+                <p><p>Creative Voice File is a container file format for digital audio<br />
+wave data. Initial revisions were able to support only unsigned<br />
+8-bit PCM and ADPCM data, later versions were revised to add support<br />
 for 16-bit PCM and a-law / u-law formats.</p>
-<p>This format was actively used in 1990s, around the advent of
-Creative's sound cards (Sound Blaster family). It was a popular
-choice for a digital sound container in lots of games and multimedia
-software due to simplicity and availability of Creative's recording
+<p>This format was actively used in 1990s, around the advent of<br />
+Creative's sound cards (Sound Blaster family). It was a popular<br />
+choice for a digital sound container in lots of games and multimedia<br />
+software due to simplicity and availability of Creative's recording<br />
 / editing tools.</p>
 </p>
             </div>
@@ -641,7 +641,7 @@ <h3>creative_voice_file.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/cpp_stl_11.html b/dbf/cpp_stl_11.html
index 584ed0d62..c0e2d579f 100644
--- a/dbf/cpp_stl_11.html
+++ b/dbf/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -890,7 +890,7 @@ <h3>dbf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/cpp_stl_98.html b/dbf/cpp_stl_98.html
index 10031a0a0..de74e1661 100644
--- a/dbf/cpp_stl_98.html
+++ b/dbf/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -973,7 +973,7 @@ <h3>dbf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/csharp.html b/dbf/csharp.html
index 9a3077c96..39d62b30a 100644
--- a/dbf/csharp.html
+++ b/dbf/csharp.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -671,7 +671,7 @@ <h3>Dbf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/go.html b/dbf/go.html
index d97ca469c..343abe5ce 100644
--- a/dbf/go.html
+++ b/dbf/go.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -741,7 +741,7 @@ <h3>dbf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/index.html b/dbf/index.html
index 7549bd19b..5705e6cef 100644
--- a/dbf/index.html
+++ b/dbf/index.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -409,7 +409,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/java.html b/dbf/java.html
index 5618d5f7e..806e85589 100644
--- a/dbf/java.html
+++ b/dbf/java.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -709,7 +709,7 @@ <h3>Dbf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/javascript.html b/dbf/javascript.html
index 1ef92c9a1..ea80991b3 100644
--- a/dbf/javascript.html
+++ b/dbf/javascript.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -531,7 +531,7 @@ <h3>Dbf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/lua.html b/dbf/lua.html
index 3e25f8897..23c891b97 100644
--- a/dbf/lua.html
+++ b/dbf/lua.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -476,7 +476,7 @@ <h3>dbf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/nim.html b/dbf/nim.html
index cede8963a..59b58519f 100644
--- a/dbf/nim.html
+++ b/dbf/nim.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -555,7 +555,7 @@ <h3>dbf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/perl.html b/dbf/perl.html
index fbe0fd8c4..06499329a 100644
--- a/dbf/perl.html
+++ b/dbf/perl.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -786,7 +786,7 @@ <h3>Dbf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/php.html b/dbf/php.html
index 1499bf391..bd371c299 100644
--- a/dbf/php.html
+++ b/dbf/php.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -543,7 +543,7 @@ <h3>Dbf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/python.html b/dbf/python.html
index 8000bd8ae..073cded97 100644
--- a/dbf/python.html
+++ b/dbf/python.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -495,7 +495,7 @@ <h3>dbf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dbf/ruby.html b/dbf/ruby.html
index 3962a37bd..ce0f23cf3 100644
--- a/dbf/ruby.html
+++ b/dbf/ruby.html
@@ -105,9 +105,9 @@ <h1>.dbf file format of dBASE:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.dbf is a relational database format introduced in DOS database
+                <p><p>.dbf is a relational database format introduced in DOS database<br />
 management system dBASE in 1982.</p>
-<p>One .dbf file corresponds to one table and contains a series of headers,
+<p>One .dbf file corresponds to one table and contains a series of headers,<br />
 specification of fields, and a number of fixed-size records.</p>
 </p>
             </div>
@@ -529,7 +529,7 @@ <h3>dbf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/cpp_stl_11.html b/dcmp_0/cpp_stl_11.html
index fbc6042bf..f1a6054f3 100644
--- a/dcmp_0/cpp_stl_11.html
+++ b/dcmp_0/cpp_stl_11.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1792,7 +1792,7 @@ <h3>dcmp_0.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/csharp.html b/dcmp_0/csharp.html
index d657563f2..c43e68396 100644
--- a/dcmp_0/csharp.html
+++ b/dcmp_0/csharp.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1401,7 +1401,7 @@ <h3>Dcmp0.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/go.html b/dcmp_0/go.html
index aad0e1a87..187d34ae4 100644
--- a/dcmp_0/go.html
+++ b/dcmp_0/go.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1469,7 +1469,7 @@ <h3>dcmp_0.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/graphviz.html b/dcmp_0/graphviz.html
index 3321e5529..6df565404 100644
--- a/dcmp_0/graphviz.html
+++ b/dcmp_0/graphviz.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -558,7 +558,7 @@ <h3>dcmp_0.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/index.html b/dcmp_0/index.html
index 4724d4777..4b2dd1862 100644
--- a/dcmp_0/index.html
+++ b/dcmp_0/index.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -795,7 +795,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/java.html b/dcmp_0/java.html
index a9f8440a1..fca1bb0cb 100644
--- a/dcmp_0/java.html
+++ b/dcmp_0/java.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1351,7 +1351,7 @@ <h3>Dcmp0.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/javascript.html b/dcmp_0/javascript.html
index 61c6ce3c8..869d2ba98 100644
--- a/dcmp_0/javascript.html
+++ b/dcmp_0/javascript.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1159,7 +1159,7 @@ <h3>Dcmp0.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/lua.html b/dcmp_0/lua.html
index 2568ec359..46da7503b 100644
--- a/dcmp_0/lua.html
+++ b/dcmp_0/lua.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1021,7 +1021,7 @@ <h3>dcmp_0.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/nim.html b/dcmp_0/nim.html
index 694e9950a..53f62d3d4 100644
--- a/dcmp_0/nim.html
+++ b/dcmp_0/nim.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1250,7 +1250,7 @@ <h3>dcmp_0.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/perl.html b/dcmp_0/perl.html
index 17a1d2484..0fe42187e 100644
--- a/dcmp_0/perl.html
+++ b/dcmp_0/perl.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -982,7 +982,7 @@ <h3>Dcmp0.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/php.html b/dcmp_0/php.html
index c0404f29a..9856e6373 100644
--- a/dcmp_0/php.html
+++ b/dcmp_0/php.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1110,7 +1110,7 @@ <h3>Dcmp0.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/python.html b/dcmp_0/python.html
index f0e5b0f53..cdfba91ea 100644
--- a/dcmp_0/python.html
+++ b/dcmp_0/python.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -885,7 +885,7 @@ <h3>dcmp_0.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_0/ruby.html b/dcmp_0/ruby.html
index 22fc347e5..5dfdc39d9 100644
--- a/dcmp_0/ruby.html
+++ b/dcmp_0/ruby.html
@@ -105,27 +105,27 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (0)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (0)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>0</code>.</p>
-<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for most compressed resources in System 7.0's files.
-This decompressor is also included with and used by some other Apple applications,
+<p>The <code>'dcmp' (0)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for most compressed resources in System 7.0's files.<br />
+This decompressor is also included with and used by some other Apple applications,<br />
 such as ResEdit.</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data,
-run-length encoding,
-and delta encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
-including a set of single-byte codes that correspond to entries in a hard-coded lookup table,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data,<br />
+run-length encoding,<br />
+and delta encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
+including a set of single-byte codes that correspond to entries in a hard-coded lookup table,<br />
 and a specialized kind of delta encoding for segment loader jump tables.</p>
-<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.
-As a result,
-it is nearly impossible to store data with an odd length in this format.
-To work around this limitation,
-odd-length resources are padded with an extra byte before compressing them with this format.
-This extra byte is ignored after decompression,
+<p>Almost all parts of this compression format operate on units of 2 or 4 bytes.<br />
+As a result,<br />
+it is nearly impossible to store data with an odd length in this format.<br />
+To work around this limitation,<br />
+odd-length resources are padded with an extra byte before compressing them with this format.<br />
+This extra byte is ignored after decompression,<br />
 as the real (odd) length of the resource is stored in the compressed resource header.</p>
-<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,
+<p>The <code>'dcmp' (1)</code> compression format (see dcmp_1.ksy) is very similar to this format,<br />
 with the main difference that it operates mostly on single bytes rather than two-byte units.</p>
 </p>
             </div>
@@ -1000,7 +1000,7 @@ <h3>dcmp_0.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/cpp_stl_11.html b/dcmp_1/cpp_stl_11.html
index 7eeaeb7d7..464cb0e37 100644
--- a/dcmp_1/cpp_stl_11.html
+++ b/dcmp_1/cpp_stl_11.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -1299,7 +1299,7 @@ <h3>dcmp_1.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/csharp.html b/dcmp_1/csharp.html
index b994243ef..72f45f867 100644
--- a/dcmp_1/csharp.html
+++ b/dcmp_1/csharp.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -992,7 +992,7 @@ <h3>Dcmp1.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/go.html b/dcmp_1/go.html
index b74f74741..fc3e41299 100644
--- a/dcmp_1/go.html
+++ b/dcmp_1/go.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -1022,7 +1022,7 @@ <h3>dcmp_1.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/graphviz.html b/dcmp_1/graphviz.html
index bab791286..79978a0bb 100644
--- a/dcmp_1/graphviz.html
+++ b/dcmp_1/graphviz.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -456,7 +456,7 @@ <h3>dcmp_1.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/index.html b/dcmp_1/index.html
index 8514113ae..ba2fa0472 100644
--- a/dcmp_1/index.html
+++ b/dcmp_1/index.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -572,7 +572,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/java.html b/dcmp_1/java.html
index 2e40b2390..7e81b5388 100644
--- a/dcmp_1/java.html
+++ b/dcmp_1/java.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -976,7 +976,7 @@ <h3>Dcmp1.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/javascript.html b/dcmp_1/javascript.html
index ca9da31ad..e62716f10 100644
--- a/dcmp_1/javascript.html
+++ b/dcmp_1/javascript.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -844,7 +844,7 @@ <h3>Dcmp1.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/lua.html b/dcmp_1/lua.html
index 39fd93dae..ae4ca6d0c 100644
--- a/dcmp_1/lua.html
+++ b/dcmp_1/lua.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -742,7 +742,7 @@ <h3>dcmp_1.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/nim.html b/dcmp_1/nim.html
index 7b5a5246e..506e501bb 100644
--- a/dcmp_1/nim.html
+++ b/dcmp_1/nim.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -878,7 +878,7 @@ <h3>dcmp_1.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/perl.html b/dcmp_1/perl.html
index 1955d2512..50a018e64 100644
--- a/dcmp_1/perl.html
+++ b/dcmp_1/perl.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -736,7 +736,7 @@ <h3>Dcmp1.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/php.html b/dcmp_1/php.html
index c5d5eb64d..4626ce846 100644
--- a/dcmp_1/php.html
+++ b/dcmp_1/php.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -786,7 +786,7 @@ <h3>Dcmp1.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/python.html b/dcmp_1/python.html
index b28ad817c..74d438742 100644
--- a/dcmp_1/python.html
+++ b/dcmp_1/python.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -686,7 +686,7 @@ <h3>dcmp_1.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_1/ruby.html b/dcmp_1/ruby.html
index 08d656e52..d706963b9 100644
--- a/dcmp_1/ruby.html
+++ b/dcmp_1/ruby.html
@@ -105,23 +105,23 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (1)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (1)</code> format,<br />
 as stored in compressed resources with header type <code>8</code> and decompressor ID <code>1</code>.</p>
-<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the Finder Help file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,
+<p>The <code>'dcmp' (1)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the Finder Help file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (1)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format supports some basic general-purpose compression schemes,
-including backreferences to previous data and run-length encoding.
-It also includes some types of compression tailored specifically to Mac OS resources,
+<p>This compression format supports some basic general-purpose compression schemes,<br />
+including backreferences to previous data and run-length encoding.<br />
+It also includes some types of compression tailored specifically to Mac OS resources,<br />
 including a set of single-byte codes that correspond to entries in a hard-coded lookup table.</p>
-<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,
-with the main difference that it operates mostly on units of 2 or 4 bytes.
-This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,
-with the latter only being used in resource files that contain mostly unaligned data,
+<p>The <code>'dcmp' (0)</code> compression format (see dcmp_0.ksy) is very similar to this format,<br />
+with the main difference that it operates mostly on units of 2 or 4 bytes.<br />
+This makes the ``dcmp' (0)<code>format more suitable for word-aligned data, such as executable code, bitmaps, sounds, etc. The</code>'dcmp' (0)` format also appears to be generally preferred over `'dcmp' (1)`,<br />
+with the latter only being used in resource files that contain mostly unaligned data,<br />
 such as text.</p>
 </p>
             </div>
@@ -739,7 +739,7 @@ <h3>dcmp_1.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/cpp_stl_11.html b/dcmp_2/cpp_stl_11.html
index 488483312..c31a12c51 100644
--- a/dcmp_2/cpp_stl_11.html
+++ b/dcmp_2/cpp_stl_11.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -1037,7 +1037,7 @@ <h3>dcmp_2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/csharp.html b/dcmp_2/csharp.html
index 7f4fd9f4c..37b20d582 100644
--- a/dcmp_2/csharp.html
+++ b/dcmp_2/csharp.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -813,7 +813,7 @@ <h3>Dcmp2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/go.html b/dcmp_2/go.html
index 9db31e5da..caae50482 100644
--- a/dcmp_2/go.html
+++ b/dcmp_2/go.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -877,7 +877,7 @@ <h3>dcmp_2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/graphviz.html b/dcmp_2/graphviz.html
index 22c747584..a12191e26 100644
--- a/dcmp_2/graphviz.html
+++ b/dcmp_2/graphviz.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -385,7 +385,7 @@ <h3>dcmp_2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/index.html b/dcmp_2/index.html
index 6139b472c..47129bf39 100644
--- a/dcmp_2/index.html
+++ b/dcmp_2/index.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -547,7 +547,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/java.html b/dcmp_2/java.html
index 752635a82..8c77c1aaf 100644
--- a/dcmp_2/java.html
+++ b/dcmp_2/java.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -801,7 +801,7 @@ <h3>Dcmp2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/javascript.html b/dcmp_2/javascript.html
index 03ddbbf41..a0507e920 100644
--- a/dcmp_2/javascript.html
+++ b/dcmp_2/javascript.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -693,7 +693,7 @@ <h3>Dcmp2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/lua.html b/dcmp_2/lua.html
index 9d6381782..3e341cc22 100644
--- a/dcmp_2/lua.html
+++ b/dcmp_2/lua.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -599,7 +599,7 @@ <h3>dcmp_2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/nim.html b/dcmp_2/nim.html
index 64be4954e..a09754b7c 100644
--- a/dcmp_2/nim.html
+++ b/dcmp_2/nim.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -706,7 +706,7 @@ <h3>dcmp_2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/perl.html b/dcmp_2/perl.html
index 95fddd34b..9646b2f7b 100644
--- a/dcmp_2/perl.html
+++ b/dcmp_2/perl.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -652,7 +652,7 @@ <h3>Dcmp2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/php.html b/dcmp_2/php.html
index e567bf378..3d01e33ba 100644
--- a/dcmp_2/php.html
+++ b/dcmp_2/php.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -657,7 +657,7 @@ <h3>Dcmp2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/python.html b/dcmp_2/python.html
index 2ce813281..734c8de20 100644
--- a/dcmp_2/python.html
+++ b/dcmp_2/python.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -552,7 +552,7 @@ <h3>dcmp_2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_2/ruby.html b/dcmp_2/ruby.html
index 90715a525..f53305423 100644
--- a/dcmp_2/ruby.html
+++ b/dcmp_2/ruby.html
@@ -105,22 +105,22 @@ <h1>Compressed Macintosh resource data, Apple `'dcmp' (2)` format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,
+                <p><p>Compressed resource data in <code>'dcmp' (2)</code> format,<br />
 as stored in compressed resources with header type <code>9</code> and decompressor ID <code>2</code>.</p>
-<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.
-This compression format is used for a few compressed resources in System 7.0's files
-(such as the System file).
-This decompressor is also included with and used by some other Apple applications,
-such as ResEdit.
-(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,
+<p>The <code>'dcmp' (2)</code> decompressor resource is included in the System file of System 7.0 and later.<br />
+This compression format is used for a few compressed resources in System 7.0's files<br />
+(such as the System file).<br />
+This decompressor is also included with and used by some other Apple applications,<br />
+such as ResEdit.<br />
+(Note: ResEdit includes the <code>'dcmp' (2)</code> resource,<br />
 but none of its resources actually use this decompressor.)</p>
-<p>This compression format is based on simple dictionary coding,
-where each byte in the compressed data expands to two bytes,
-based on a lookup table
-(either included in the compressed data or provided by the decompressor).
-An alternative &quot;tagged&quot; compression format is also supported,
-which allows using two-byte literals in addition to single-byte table references,
-at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,
+<p>This compression format is based on simple dictionary coding,<br />
+where each byte in the compressed data expands to two bytes,<br />
+based on a lookup table<br />
+(either included in the compressed data or provided by the decompressor).<br />
+An alternative &quot;tagged&quot; compression format is also supported,<br />
+which allows using two-byte literals in addition to single-byte table references,<br />
+at the cost of requiring an extra &quot;tag&quot; byte every 16 output bytes,<br />
 to differentiate literals and table references.</p>
 </p>
             </div>
@@ -635,7 +635,7 @@ <h3>dcmp_2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/cpp_stl_11.html b/dcmp_variable_length_integer/cpp_stl_11.html
index 6fb6f9840..7367d4fe7 100644
--- a/dcmp_variable_length_integer/cpp_stl_11.html
+++ b/dcmp_variable_length_integer/cpp_stl_11.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -530,7 +530,7 @@ <h3>dcmp_variable_length_integer.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/cpp_stl_98.html b/dcmp_variable_length_integer/cpp_stl_98.html
index 0995db746..6bd84c1fa 100644
--- a/dcmp_variable_length_integer/cpp_stl_98.html
+++ b/dcmp_variable_length_integer/cpp_stl_98.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -538,7 +538,7 @@ <h3>dcmp_variable_length_integer.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/csharp.html b/dcmp_variable_length_integer/csharp.html
index 23ae14b2a..6239bec7e 100644
--- a/dcmp_variable_length_integer/csharp.html
+++ b/dcmp_variable_length_integer/csharp.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -443,7 +443,7 @@ <h3>DcmpVariableLengthInteger.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/go.html b/dcmp_variable_length_integer/go.html
index 478466ab7..0f969452b 100644
--- a/dcmp_variable_length_integer/go.html
+++ b/dcmp_variable_length_integer/go.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -392,7 +392,7 @@ <h3>dcmp_variable_length_integer.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/graphviz.html b/dcmp_variable_length_integer/graphviz.html
index efb059928..7aaca2b15 100644
--- a/dcmp_variable_length_integer/graphviz.html
+++ b/dcmp_variable_length_integer/graphviz.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -302,7 +302,7 @@ <h3>dcmp_variable_length_integer.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/index.html b/dcmp_variable_length_integer/index.html
index f29ab9db4..4d62af35c 100644
--- a/dcmp_variable_length_integer/index.html
+++ b/dcmp_variable_length_integer/index.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -328,7 +328,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/java.html b/dcmp_variable_length_integer/java.html
index 05dee745f..8daee5905 100644
--- a/dcmp_variable_length_integer/java.html
+++ b/dcmp_variable_length_integer/java.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>DcmpVariableLengthInteger.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/javascript.html b/dcmp_variable_length_integer/javascript.html
index 4a924bfc3..c2ab35adb 100644
--- a/dcmp_variable_length_integer/javascript.html
+++ b/dcmp_variable_length_integer/javascript.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -424,7 +424,7 @@ <h3>DcmpVariableLengthInteger.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/lua.html b/dcmp_variable_length_integer/lua.html
index c89afde69..058299b9f 100644
--- a/dcmp_variable_length_integer/lua.html
+++ b/dcmp_variable_length_integer/lua.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -357,7 +357,7 @@ <h3>dcmp_variable_length_integer.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/nim.html b/dcmp_variable_length_integer/nim.html
index b8c67416e..73668f237 100644
--- a/dcmp_variable_length_integer/nim.html
+++ b/dcmp_variable_length_integer/nim.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -375,7 +375,7 @@ <h3>dcmp_variable_length_integer.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/perl.html b/dcmp_variable_length_integer/perl.html
index 4e165368b..719356b1b 100644
--- a/dcmp_variable_length_integer/perl.html
+++ b/dcmp_variable_length_integer/perl.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -339,7 +339,7 @@ <h3>DcmpVariableLengthInteger.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/php.html b/dcmp_variable_length_integer/php.html
index 673b3a8d2..457def628 100644
--- a/dcmp_variable_length_integer/php.html
+++ b/dcmp_variable_length_integer/php.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -361,7 +361,7 @@ <h3>DcmpVariableLengthInteger.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/python.html b/dcmp_variable_length_integer/python.html
index de98e60d8..5692c18b6 100644
--- a/dcmp_variable_length_integer/python.html
+++ b/dcmp_variable_length_integer/python.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -388,7 +388,7 @@ <h3>dcmp_variable_length_integer.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dcmp_variable_length_integer/ruby.html b/dcmp_variable_length_integer/ruby.html
index 85020b271..6b7e3bdc0 100644
--- a/dcmp_variable_length_integer/ruby.html
+++ b/dcmp_variable_length_integer/ruby.html
@@ -105,22 +105,22 @@ <h1>Variable-length integer used in Apple `'dcmp' (0)` and `'dcmp' (1)` compress
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length integer,
-in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.
+                <p><p>A variable-length integer,<br />
+in the format used by the 0xfe chunks in the <code>'dcmp' (0)</code> and <code>'dcmp' (1)</code> resource compression formats.<br />
 See the dcmp_0 and dcmp_1 specs for more information about these compression formats.</p>
 <p>This variable-length integer format can store an integer <code>x</code> in any of the following ways:</p>
 <ul>
-<li>In a single byte,
-if <code>0 &lt;= x &lt;= 0x7f</code>
+<li>In a single byte,<br />
+if <code>0 &lt;= x &lt;= 0x7f</code><br />
 (7-bit unsigned integer)</li>
-<li>In 2 bytes,
-if <code>-0x4000 &lt;= x &lt;= 0x3eff</code>
+<li>In 2 bytes,<br />
+if <code>-0x4000 &lt;= x &lt;= 0x3eff</code><br />
 (15-bit signed integer with the highest <code>0x100</code> values unavailable)</li>
-<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code>
+<li>In 5 bytes, if <code>-0x80000000 &lt;= x &lt;= 0x7fffffff</code><br />
 (32-bit signed integer)</li>
 </ul>
-<p>In practice,
-values are always stored in the smallest possible format,
+<p>In practice,<br />
+values are always stored in the smallest possible format,<br />
 but technically any of the larger formats could be used as well.</p>
 </p>
             </div>
@@ -412,7 +412,7 @@ <h3>dcmp_variable_length_integer.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/csharp.html b/dex/csharp.html
index 096f6b4de..5e25beea6 100644
--- a/dex/csharp.html
+++ b/dex/csharp.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -2105,7 +2105,7 @@ <h3>Dex.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/go.html b/dex/go.html
index d4f83a6b0..3895012f5 100644
--- a/dex/go.html
+++ b/dex/go.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -2467,7 +2467,7 @@ <h3>dex.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/graphviz.html b/dex/graphviz.html
index c059d03d2..023af6280 100644
--- a/dex/graphviz.html
+++ b/dex/graphviz.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -728,7 +728,7 @@ <h3>dex.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/index.html b/dex/index.html
index 1a2a61928..99cbe0850 100644
--- a/dex/index.html
+++ b/dex/index.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1018,7 +1018,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/java.html b/dex/java.html
index 37579e10d..f4261ded3 100644
--- a/dex/java.html
+++ b/dex/java.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -2078,7 +2078,7 @@ <h3>Dex.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/javascript.html b/dex/javascript.html
index d25016e43..2ce547f04 100644
--- a/dex/javascript.html
+++ b/dex/javascript.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1666,7 +1666,7 @@ <h3>Dex.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/lua.html b/dex/lua.html
index 037c105ea..4c711363d 100644
--- a/dex/lua.html
+++ b/dex/lua.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1411,7 +1411,7 @@ <h3>dex.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/nim.html b/dex/nim.html
index 5ebde8b35..c43809559 100644
--- a/dex/nim.html
+++ b/dex/nim.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1846,7 +1846,7 @@ <h3>dex.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/perl.html b/dex/perl.html
index fdfce94e9..231d00c70 100644
--- a/dex/perl.html
+++ b/dex/perl.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1838,7 +1838,7 @@ <h3>Dex.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/php.html b/dex/php.html
index a355594f8..3a1f5d242 100644
--- a/dex/php.html
+++ b/dex/php.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1670,7 +1670,7 @@ <h3>Dex.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/python.html b/dex/python.html
index 09af01b6d..cf227a902 100644
--- a/dex/python.html
+++ b/dex/python.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1088,7 +1088,7 @@ <h3>dex.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dex/ruby.html b/dex/ruby.html
index 256526c96..9c5738fd9 100644
--- a/dex/ruby.html
+++ b/dex/ruby.html
@@ -105,11 +105,11 @@ <h1>Android Dalvik VM executable (dex):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Android OS applications executables are typically stored in its own
-format, optimized for more efficient execution in Dalvik virtual
+                <p><p>Android OS applications executables are typically stored in its own<br />
+format, optimized for more efficient execution in Dalvik virtual<br />
 machine.</p>
-<p>This format is loosely similar to Java .class file format and
-generally holds the similar set of data: i.e. classes, methods,
+<p>This format is loosely similar to Java .class file format and<br />
+generally holds the similar set of data: i.e. classes, methods,<br />
 fields, annotations, etc.</p>
 </p>
             </div>
@@ -1436,7 +1436,7 @@ <h3>dex.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/cpp_stl_11.html b/dicom/cpp_stl_11.html
index 862745318..6161dc8da 100644
--- a/dicom/cpp_stl_11.html
+++ b/dicom/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -5100,7 +5100,7 @@ <h3>dicom.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/cpp_stl_98.html b/dicom/cpp_stl_98.html
index 2dbeadd2e..5ae566d4e 100644
--- a/dicom/cpp_stl_98.html
+++ b/dicom/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -5171,7 +5171,7 @@ <h3>dicom.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/csharp.html b/dicom/csharp.html
index 37eee046a..29bdc60d6 100644
--- a/dicom/csharp.html
+++ b/dicom/csharp.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4791,7 +4791,7 @@ <h3>Dicom.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/go.html b/dicom/go.html
index 0ccf34412..cb88791f0 100644
--- a/dicom/go.html
+++ b/dicom/go.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4836,7 +4836,7 @@ <h3>dicom.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/graphviz.html b/dicom/graphviz.html
index c42c8c6b4..18eb7217a 100644
--- a/dicom/graphviz.html
+++ b/dicom/graphviz.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -451,7 +451,7 @@ <h3>dicom.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/index.html b/dicom/index.html
index 0a4ed2fc1..c9470a58d 100644
--- a/dicom/index.html
+++ b/dicom/index.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4465,7 +4465,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/java.html b/dicom/java.html
index 476583e07..3a7ebcdf6 100644
--- a/dicom/java.html
+++ b/dicom/java.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4768,7 +4768,7 @@ <h3>Dicom.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/javascript.html b/dicom/javascript.html
index f8c4be3b5..64bf850bd 100644
--- a/dicom/javascript.html
+++ b/dicom/javascript.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -8652,7 +8652,7 @@ <h3>Dicom.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/lua.html b/dicom/lua.html
index 2bcd0bad1..cef811e38 100644
--- a/dicom/lua.html
+++ b/dicom/lua.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4597,7 +4597,7 @@ <h3>dicom.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/nim.html b/dicom/nim.html
index aabf1918c..1712469e7 100644
--- a/dicom/nim.html
+++ b/dicom/nim.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4641,7 +4641,7 @@ <h3>dicom.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/perl.html b/dicom/perl.html
index 6b0f3ba93..a79034be7 100644
--- a/dicom/perl.html
+++ b/dicom/perl.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4747,7 +4747,7 @@ <h3>Dicom.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/php.html b/dicom/php.html
index f887c55d6..a5db78cc3 100644
--- a/dicom/php.html
+++ b/dicom/php.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4603,7 +4603,7 @@ <h3>Dicom.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/python.html b/dicom/python.html
index 4bdf91d5a..ae801ba66 100644
--- a/dicom/python.html
+++ b/dicom/python.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4601,7 +4601,7 @@ <h3>dicom.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dicom/ruby.html b/dicom/ruby.html
index 66808ab6f..7f84d8627 100644
--- a/dicom/ruby.html
+++ b/dicom/ruby.html
@@ -105,14 +105,14 @@ <h1>Digital Imaging and Communications in Medicine (DICOM) file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA
-PS3, AKA ISO 12052:2006, is a file format and network protocol
-standard for medical imaging purposes. This parser covers file
-format, typically written by various medical equipment, such as
+                <p><p>DICOM (Digital Imaging and Communications in Medicine), AKA NEMA<br />
+PS3, AKA ISO 12052:2006, is a file format and network protocol<br />
+standard for medical imaging purposes. This parser covers file<br />
+format, typically written by various medical equipment, such as<br />
 radiography, computer tomography scans, MRT, ultrasonography, etc.</p>
-<p>DICOM defines two transfer syntaxes: implicit and explicit. This
-top-level parser attempts to autodetect and handle both of them. If
-any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code>
+<p>DICOM defines two transfer syntaxes: implicit and explicit. This<br />
+top-level parser attempts to autodetect and handle both of them. If<br />
+any problems arise, one can use <code>file_explicit</code> and <code>file_implicit</code><br />
 subtypes to force parsing in particular transfer syntax.</p>
 </p>
             </div>
@@ -4595,7 +4595,7 @@ <h3>dicom.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/cpp_stl_11.html b/dime_message/cpp_stl_11.html
index a9d9ea507..d701d62ce 100644
--- a/dime_message/cpp_stl_11.html
+++ b/dime_message/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -778,7 +778,7 @@ <h3>dime_message.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/cpp_stl_98.html b/dime_message/cpp_stl_98.html
index 848d4b4b7..9e3ef04b5 100644
--- a/dime_message/cpp_stl_98.html
+++ b/dime_message/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -840,7 +840,7 @@ <h3>dime_message.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/csharp.html b/dime_message/csharp.html
index b229fc77b..9f4c1fa92 100644
--- a/dime_message/csharp.html
+++ b/dime_message/csharp.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -625,7 +625,7 @@ <h3>DimeMessage.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/go.html b/dime_message/go.html
index a62949cb1..0a6fef9dd 100644
--- a/dime_message/go.html
+++ b/dime_message/go.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -657,7 +657,7 @@ <h3>dime_message.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/graphviz.html b/dime_message/graphviz.html
index f58d4d340..4d42760ca 100644
--- a/dime_message/graphviz.html
+++ b/dime_message/graphviz.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -364,7 +364,7 @@ <h3>dime_message.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/index.html b/dime_message/index.html
index 7e1649a56..bfc02ec54 100644
--- a/dime_message/index.html
+++ b/dime_message/index.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -384,7 +384,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/java.html b/dime_message/java.html
index 0e624aeec..47a0c38a8 100644
--- a/dime_message/java.html
+++ b/dime_message/java.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -659,7 +659,7 @@ <h3>DimeMessage.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/javascript.html b/dime_message/javascript.html
index 612f14205..fba383ffb 100644
--- a/dime_message/javascript.html
+++ b/dime_message/javascript.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -537,7 +537,7 @@ <h3>DimeMessage.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/lua.html b/dime_message/lua.html
index c8d30df79..7b41522e6 100644
--- a/dime_message/lua.html
+++ b/dime_message/lua.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -448,7 +448,7 @@ <h3>dime_message.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/nim.html b/dime_message/nim.html
index dc9ea23b7..6a617d288 100644
--- a/dime_message/nim.html
+++ b/dime_message/nim.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -538,7 +538,7 @@ <h3>dime_message.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/perl.html b/dime_message/perl.html
index 628fc2592..a23459b2d 100644
--- a/dime_message/perl.html
+++ b/dime_message/perl.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -614,7 +614,7 @@ <h3>DimeMessage.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/php.html b/dime_message/php.html
index 1f08d15f6..8f26ec44f 100644
--- a/dime_message/php.html
+++ b/dime_message/php.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -521,7 +521,7 @@ <h3>DimeMessage.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/python.html b/dime_message/python.html
index bb30bdb90..854aec689 100644
--- a/dime_message/python.html
+++ b/dime_message/python.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -452,7 +452,7 @@ <h3>dime_message.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dime_message/ruby.html b/dime_message/ruby.html
index 840ed853b..049b8535a 100644
--- a/dime_message/ruby.html
+++ b/dime_message/ruby.html
@@ -105,10 +105,10 @@ <h1>DIME (Direct Internet Message Encapsulation) Message:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Direct Internet Message Encapsulation (DIME)
-is an old Microsoft specification for sending and receiving
-SOAP messages along with additional attachments,
-like binary files, XML fragments, and even other
+                <p><p>Direct Internet Message Encapsulation (DIME)<br />
+is an old Microsoft specification for sending and receiving<br />
+SOAP messages along with additional attachments,<br />
+like binary files, XML fragments, and even other<br />
 SOAP messages, using standard transport protocols like HTTP.</p>
 <p>Sample file: <code>curl -LO https://github.com/kaitai-io/kaitai_struct_formats/files/5894723/scanner_withoptions.dump.gz &amp;&amp; gunzip scanner_withoptions.dump.gz</code></p>
 </p>
@@ -518,7 +518,7 @@ <h3>dime_message.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/cpp_stl_11.html b/dns_packet/cpp_stl_11.html
index 9f5e5732d..c510cb108 100644
--- a/dns_packet/cpp_stl_11.html
+++ b/dns_packet/cpp_stl_11.html
@@ -1593,7 +1593,7 @@ <h3>dns_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/cpp_stl_98.html b/dns_packet/cpp_stl_98.html
index 438850621..0d9a82acd 100644
--- a/dns_packet/cpp_stl_98.html
+++ b/dns_packet/cpp_stl_98.html
@@ -1748,7 +1748,7 @@ <h3>dns_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/csharp.html b/dns_packet/csharp.html
index 27eb317d8..8dd52e55d 100644
--- a/dns_packet/csharp.html
+++ b/dns_packet/csharp.html
@@ -1119,7 +1119,7 @@ <h3>DnsPacket.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/go.html b/dns_packet/go.html
index b7ca4d70d..e33b881d1 100644
--- a/dns_packet/go.html
+++ b/dns_packet/go.html
@@ -1249,7 +1249,7 @@ <h3>dns_packet.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/graphviz.html b/dns_packet/graphviz.html
index 945284868..213535d0c 100644
--- a/dns_packet/graphviz.html
+++ b/dns_packet/graphviz.html
@@ -549,7 +549,7 @@ <h3>dns_packet.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/index.html b/dns_packet/index.html
index e7e3e4af8..3f4a4c0c9 100644
--- a/dns_packet/index.html
+++ b/dns_packet/index.html
@@ -488,7 +488,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/java.html b/dns_packet/java.html
index 8ca70cbdd..b8d1ba13c 100644
--- a/dns_packet/java.html
+++ b/dns_packet/java.html
@@ -1137,7 +1137,7 @@ <h3>DnsPacket.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/javascript.html b/dns_packet/javascript.html
index ab1a57eeb..5d197e20d 100644
--- a/dns_packet/javascript.html
+++ b/dns_packet/javascript.html
@@ -860,7 +860,7 @@ <h3>DnsPacket.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/lua.html b/dns_packet/lua.html
index 6a6bbbac0..d682147e1 100644
--- a/dns_packet/lua.html
+++ b/dns_packet/lua.html
@@ -774,7 +774,7 @@ <h3>dns_packet.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/nim.html b/dns_packet/nim.html
index f8d5eee45..46a7b95dc 100644
--- a/dns_packet/nim.html
+++ b/dns_packet/nim.html
@@ -917,7 +917,7 @@ <h3>dns_packet.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/perl.html b/dns_packet/perl.html
index 4be97d4ef..57b262e42 100644
--- a/dns_packet/perl.html
+++ b/dns_packet/perl.html
@@ -1199,7 +1199,7 @@ <h3>DnsPacket.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/php.html b/dns_packet/php.html
index c4d8aa540..59812d9fb 100644
--- a/dns_packet/php.html
+++ b/dns_packet/php.html
@@ -842,7 +842,7 @@ <h3>DnsPacket.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/python.html b/dns_packet/python.html
index 8049d5182..25ce26ad6 100644
--- a/dns_packet/python.html
+++ b/dns_packet/python.html
@@ -722,7 +722,7 @@ <h3>dns_packet.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dns_packet/ruby.html b/dns_packet/ruby.html
index 1ff7304ab..31a84ff05 100644
--- a/dns_packet/ruby.html
+++ b/dns_packet/ruby.html
@@ -764,7 +764,7 @@ <h3>dns_packet.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/cpp_stl_11.html b/doom_wad/cpp_stl_11.html
index 6de247ed2..925da19b8 100644
--- a/doom_wad/cpp_stl_11.html
+++ b/doom_wad/cpp_stl_11.html
@@ -1667,7 +1667,7 @@ <h3>doom_wad.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/cpp_stl_98.html b/doom_wad/cpp_stl_98.html
index 70af66f4e..472ff7483 100644
--- a/doom_wad/cpp_stl_98.html
+++ b/doom_wad/cpp_stl_98.html
@@ -1852,7 +1852,7 @@ <h3>doom_wad.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/csharp.html b/doom_wad/csharp.html
index 3167ee278..e5cf3bafd 100644
--- a/doom_wad/csharp.html
+++ b/doom_wad/csharp.html
@@ -1230,7 +1230,7 @@ <h3>DoomWad.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/go.html b/doom_wad/go.html
index 5155382d7..b03e9c12b 100644
--- a/doom_wad/go.html
+++ b/doom_wad/go.html
@@ -1425,7 +1425,7 @@ <h3>doom_wad.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/graphviz.html b/doom_wad/graphviz.html
index fc6c691d2..8a21eb6fa 100644
--- a/doom_wad/graphviz.html
+++ b/doom_wad/graphviz.html
@@ -570,7 +570,7 @@ <h3>doom_wad.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/index.html b/doom_wad/index.html
index 6169fd6bd..46c3e7d01 100644
--- a/doom_wad/index.html
+++ b/doom_wad/index.html
@@ -570,7 +570,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/java.html b/doom_wad/java.html
index 1a638a525..97eec0c2f 100644
--- a/doom_wad/java.html
+++ b/doom_wad/java.html
@@ -1305,7 +1305,7 @@ <h3>DoomWad.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/javascript.html b/doom_wad/javascript.html
index 3bf446091..0616f40d5 100644
--- a/doom_wad/javascript.html
+++ b/doom_wad/javascript.html
@@ -945,7 +945,7 @@ <h3>DoomWad.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/lua.html b/doom_wad/lua.html
index f8cdca5e1..138572ec6 100644
--- a/doom_wad/lua.html
+++ b/doom_wad/lua.html
@@ -818,7 +818,7 @@ <h3>doom_wad.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/nim.html b/doom_wad/nim.html
index 32bb1ab1f..4c74139e5 100644
--- a/doom_wad/nim.html
+++ b/doom_wad/nim.html
@@ -1023,7 +1023,7 @@ <h3>doom_wad.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/perl.html b/doom_wad/perl.html
index 1ee55b4ab..c507e1c70 100644
--- a/doom_wad/perl.html
+++ b/doom_wad/perl.html
@@ -1423,7 +1423,7 @@ <h3>DoomWad.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/php.html b/doom_wad/php.html
index 2b64c972a..b0f54f48f 100644
--- a/doom_wad/php.html
+++ b/doom_wad/php.html
@@ -955,7 +955,7 @@ <h3>DoomWad.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/python.html b/doom_wad/python.html
index def4a4cea..ed4de18c3 100644
--- a/doom_wad/python.html
+++ b/doom_wad/python.html
@@ -756,7 +756,7 @@ <h3>doom_wad.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/doom_wad/ruby.html b/doom_wad/ruby.html
index 00d555ae9..4d329d0d0 100644
--- a/doom_wad/ruby.html
+++ b/doom_wad/ruby.html
@@ -863,7 +863,7 @@ <h3>doom_wad.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/cpp_stl_11.html b/dos_datetime/cpp_stl_11.html
index ff2109f25..f696315a2 100644
--- a/dos_datetime/cpp_stl_11.html
+++ b/dos_datetime/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -743,7 +743,7 @@ <h3>dos_datetime.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/cpp_stl_98.html b/dos_datetime/cpp_stl_98.html
index bee7c5a60..1b67399b7 100644
--- a/dos_datetime/cpp_stl_98.html
+++ b/dos_datetime/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -769,7 +769,7 @@ <h3>dos_datetime.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/csharp.html b/dos_datetime/csharp.html
index 12ae9bd3b..467f134dc 100644
--- a/dos_datetime/csharp.html
+++ b/dos_datetime/csharp.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -625,7 +625,7 @@ <h3>DosDatetime.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/go.html b/dos_datetime/go.html
index b4503b9d7..2a9f3ca60 100644
--- a/dos_datetime/go.html
+++ b/dos_datetime/go.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -623,7 +623,7 @@ <h3>dos_datetime.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/graphviz.html b/dos_datetime/graphviz.html
index 9f1f15137..f632a591e 100644
--- a/dos_datetime/graphviz.html
+++ b/dos_datetime/graphviz.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -392,7 +392,7 @@ <h3>dos_datetime.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/index.html b/dos_datetime/index.html
index 9be9a1c7b..8109319bf 100644
--- a/dos_datetime/index.html
+++ b/dos_datetime/index.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -398,7 +398,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/java.html b/dos_datetime/java.html
index 61067eb75..be1a8a12f 100644
--- a/dos_datetime/java.html
+++ b/dos_datetime/java.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -574,7 +574,7 @@ <h3>DosDatetime.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/javascript.html b/dos_datetime/javascript.html
index de0847992..a746f0fa0 100644
--- a/dos_datetime/javascript.html
+++ b/dos_datetime/javascript.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -528,7 +528,7 @@ <h3>DosDatetime.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/lua.html b/dos_datetime/lua.html
index 8598bcd06..97468fad8 100644
--- a/dos_datetime/lua.html
+++ b/dos_datetime/lua.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -492,7 +492,7 @@ <h3>dos_datetime.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/nim.html b/dos_datetime/nim.html
index e6c1dde4b..af70cfb17 100644
--- a/dos_datetime/nim.html
+++ b/dos_datetime/nim.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -510,7 +510,7 @@ <h3>dos_datetime.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/perl.html b/dos_datetime/perl.html
index 86fa85da6..9ef248714 100644
--- a/dos_datetime/perl.html
+++ b/dos_datetime/perl.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -513,7 +513,7 @@ <h3>DosDatetime.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/php.html b/dos_datetime/php.html
index 33affe987..064db4638 100644
--- a/dos_datetime/php.html
+++ b/dos_datetime/php.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -477,7 +477,7 @@ <h3>DosDatetime.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/python.html b/dos_datetime/python.html
index 83ecb8a5f..5e1fc9bfd 100644
--- a/dos_datetime/python.html
+++ b/dos_datetime/python.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -515,7 +515,7 @@ <h3>dos_datetime.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_datetime/ruby.html b/dos_datetime/ruby.html
index 0adeacbf3..f34fe2e7f 100644
--- a/dos_datetime/ruby.html
+++ b/dos_datetime/ruby.html
@@ -105,13 +105,13 @@ <h1>MS-DOS datetime:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.
-The time is always stored in the current UTC time offset set on the computer
-which created the file. Note that the daylight saving time (DST) shifts
+                <p><p>MS-DOS date and time are packed 16-bit values that specify local date/time.<br />
+The time is always stored in the current UTC time offset set on the computer<br />
+which created the file. Note that the daylight saving time (DST) shifts<br />
 also change the UTC time offset.</p>
-<p>For example, if you pack two files A and B into a ZIP archive, file A last modified
-at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),
-the file modification times saved in MS-DOS format in the ZIP file will vary depending
+<p>For example, if you pack two files A and B into a ZIP archive, file A last modified<br />
+at 2020-03-29 00:59 UTC+00:00 (GMT) and file B at 2020-03-29 02:00 UTC+01:00 (BST),<br />
+the file modification times saved in MS-DOS format in the ZIP file will vary depending<br />
 on whether the computer packing the files is set to GMT or BST at the time of ZIP creation.</p>
 <ul>
 <li>If set to GMT:
@@ -127,8 +127,8 @@ <h1>MS-DOS datetime:
 </ul>
 </li>
 </ul>
-<p>It follows that you are unable to determine the actual last modified time
-of any file stored in the ZIP archive, if you don't know the locale time
+<p>It follows that you are unable to determine the actual last modified time<br />
+of any file stored in the ZIP archive, if you don't know the locale time<br />
 setting of the computer at the time it created the ZIP.</p>
 <p>This format is used in some data formats from the MS-DOS era, for example:</p>
 <ul>
@@ -485,7 +485,7 @@ <h3>dos_datetime.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/cpp_stl_11.html b/dos_mz/cpp_stl_11.html
index b2d16708e..5a949aeaf 100644
--- a/dos_mz/cpp_stl_11.html
+++ b/dos_mz/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -694,7 +694,7 @@ <h3>dos_mz.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/cpp_stl_98.html b/dos_mz/cpp_stl_98.html
index 72ba11d87..992e81f97 100644
--- a/dos_mz/cpp_stl_98.html
+++ b/dos_mz/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -732,7 +732,7 @@ <h3>dos_mz.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/csharp.html b/dos_mz/csharp.html
index 948573e9e..06443b2f8 100644
--- a/dos_mz/csharp.html
+++ b/dos_mz/csharp.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -545,7 +545,7 @@ <h3>DosMz.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/go.html b/dos_mz/go.html
index f3ee23e99..d2cea115e 100644
--- a/dos_mz/go.html
+++ b/dos_mz/go.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -569,7 +569,7 @@ <h3>dos_mz.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/index.html b/dos_mz/index.html
index 94880df8c..dffa21e90 100644
--- a/dos_mz/index.html
+++ b/dos_mz/index.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -362,7 +362,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/java.html b/dos_mz/java.html
index 8b0da1d84..ff2dacf51 100644
--- a/dos_mz/java.html
+++ b/dos_mz/java.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -546,7 +546,7 @@ <h3>DosMz.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/javascript.html b/dos_mz/javascript.html
index dc4280a25..85daf743c 100644
--- a/dos_mz/javascript.html
+++ b/dos_mz/javascript.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -457,7 +457,7 @@ <h3>DosMz.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/lua.html b/dos_mz/lua.html
index 06ba853b7..3c890b09a 100644
--- a/dos_mz/lua.html
+++ b/dos_mz/lua.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -413,7 +413,7 @@ <h3>dos_mz.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/nim.html b/dos_mz/nim.html
index 94f0991df..0fd7010d6 100644
--- a/dos_mz/nim.html
+++ b/dos_mz/nim.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -460,7 +460,7 @@ <h3>dos_mz.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/perl.html b/dos_mz/perl.html
index 0afa15757..e82b98dc4 100644
--- a/dos_mz/perl.html
+++ b/dos_mz/perl.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -569,7 +569,7 @@ <h3>DosMz.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/php.html b/dos_mz/php.html
index e2c85b195..4ec45c169 100644
--- a/dos_mz/php.html
+++ b/dos_mz/php.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -437,7 +437,7 @@ <h3>DosMz.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/python.html b/dos_mz/python.html
index 21355a512..bb6d92ace 100644
--- a/dos_mz/python.html
+++ b/dos_mz/python.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -440,7 +440,7 @@ <h3>dos_mz.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dos_mz/ruby.html b/dos_mz/ruby.html
index b898d7ca0..801e76c6b 100644
--- a/dos_mz/ruby.html
+++ b/dos_mz/ruby.html
@@ -105,12 +105,12 @@ <h1>DOS MZ executable:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS
-environment. Many modern formats (i.e. Windows PE) still maintain
+                <p><p>DOS MZ file format is a traditional format for executables in MS-DOS<br />
+environment. Many modern formats (i.e. Windows PE) still maintain<br />
 compatibility stub with this format.</p>
-<p>As opposed to .com file format (which basically sports one 64K code
-segment of raw CPU instructions), DOS MZ .exe file format allowed
-more flexible memory management, loading of larger programs and
+<p>As opposed to .com file format (which basically sports one 64K code<br />
+segment of raw CPU instructions), DOS MZ .exe file format allowed<br />
+more flexible memory management, loading of larger programs and<br />
 added support for relocations.</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h3>dos_mz.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/csharp.html b/ds_store/csharp.html
index eeff5c668..e9da7b64c 100644
--- a/ds_store/csharp.html
+++ b/ds_store/csharp.html
@@ -1067,7 +1067,7 @@ <h3>DsStore.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/graphviz.html b/ds_store/graphviz.html
index 4be81a50a..3af91f73f 100644
--- a/ds_store/graphviz.html
+++ b/ds_store/graphviz.html
@@ -515,7 +515,7 @@ <h3>ds_store.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/index.html b/ds_store/index.html
index cfbbbeee0..a962af6eb 100644
--- a/ds_store/index.html
+++ b/ds_store/index.html
@@ -476,7 +476,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/java.html b/ds_store/java.html
index 4b6151f68..f77faffce 100644
--- a/ds_store/java.html
+++ b/ds_store/java.html
@@ -1060,7 +1060,7 @@ <h3>DsStore.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/javascript.html b/ds_store/javascript.html
index d504f33f2..a7435a023 100644
--- a/ds_store/javascript.html
+++ b/ds_store/javascript.html
@@ -809,7 +809,7 @@ <h3>DsStore.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/lua.html b/ds_store/lua.html
index 9db7e8272..4dd143cb1 100644
--- a/ds_store/lua.html
+++ b/ds_store/lua.html
@@ -722,7 +722,7 @@ <h3>ds_store.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/nim.html b/ds_store/nim.html
index 13eaba9fc..cbffff074 100644
--- a/ds_store/nim.html
+++ b/ds_store/nim.html
@@ -875,7 +875,7 @@ <h3>ds_store.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/perl.html b/ds_store/perl.html
index 41c969e28..3ef23e51f 100644
--- a/ds_store/perl.html
+++ b/ds_store/perl.html
@@ -1124,7 +1124,7 @@ <h3>DsStore.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/php.html b/ds_store/php.html
index bd5fbf375..f3bbe0a49 100644
--- a/ds_store/php.html
+++ b/ds_store/php.html
@@ -807,7 +807,7 @@ <h3>DsStore.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/python.html b/ds_store/python.html
index f702986ff..50bcc53ff 100644
--- a/ds_store/python.html
+++ b/ds_store/python.html
@@ -672,7 +672,7 @@ <h3>ds_store.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ds_store/ruby.html b/ds_store/ruby.html
index 892d09f91..a78bc899b 100644
--- a/ds_store/ruby.html
+++ b/ds_store/ruby.html
@@ -728,7 +728,7 @@ <h3>ds_store.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/cpp_stl_11.html b/dtb/cpp_stl_11.html
index 2bd2f3cbf..e1549bf51 100644
--- a/dtb/cpp_stl_11.html
+++ b/dtb/cpp_stl_11.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -999,7 +999,7 @@ <h3>dtb.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/cpp_stl_98.html b/dtb/cpp_stl_98.html
index 8ffe15935..7c84ee8b0 100644
--- a/dtb/cpp_stl_98.html
+++ b/dtb/cpp_stl_98.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -1085,7 +1085,7 @@ <h3>dtb.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/csharp.html b/dtb/csharp.html
index e565f6634..355abc381 100644
--- a/dtb/csharp.html
+++ b/dtb/csharp.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -759,7 +759,7 @@ <h3>Dtb.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/go.html b/dtb/go.html
index dc56798c8..7908f0ffd 100644
--- a/dtb/go.html
+++ b/dtb/go.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -833,7 +833,7 @@ <h3>dtb.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/graphviz.html b/dtb/graphviz.html
index c0a72f5df..8de9fe8d1 100644
--- a/dtb/graphviz.html
+++ b/dtb/graphviz.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -439,7 +439,7 @@ <h3>dtb.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/index.html b/dtb/index.html
index 655c39447..a7d13cec4 100644
--- a/dtb/index.html
+++ b/dtb/index.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -448,7 +448,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/java.html b/dtb/java.html
index baf966903..456781330 100644
--- a/dtb/java.html
+++ b/dtb/java.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -786,7 +786,7 @@ <h3>Dtb.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/javascript.html b/dtb/javascript.html
index ecd11ef55..34c282392 100644
--- a/dtb/javascript.html
+++ b/dtb/javascript.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -619,7 +619,7 @@ <h3>Dtb.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/lua.html b/dtb/lua.html
index 0edfb59f6..80e8c3fc3 100644
--- a/dtb/lua.html
+++ b/dtb/lua.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -565,7 +565,7 @@ <h3>dtb.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/nim.html b/dtb/nim.html
index 37c787c91..505eef7b2 100644
--- a/dtb/nim.html
+++ b/dtb/nim.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -630,7 +630,7 @@ <h3>dtb.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/perl.html b/dtb/perl.html
index a9f334e95..6a3f9be0d 100644
--- a/dtb/perl.html
+++ b/dtb/perl.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -791,7 +791,7 @@ <h3>Dtb.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/php.html b/dtb/php.html
index 9c4331c97..301d3304b 100644
--- a/dtb/php.html
+++ b/dtb/php.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -596,7 +596,7 @@ <h3>Dtb.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/python.html b/dtb/python.html
index 11ffa61f5..c358d3baf 100644
--- a/dtb/python.html
+++ b/dtb/python.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -572,7 +572,7 @@ <h3>dtb.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dtb/ruby.html b/dtb/ruby.html
index 56d22dc02..4861e7bbf 100644
--- a/dtb/ruby.html
+++ b/dtb/ruby.html
@@ -105,18 +105,18 @@ <h1>Flattened Devicetree Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding
-of data (primarily devicetree data, although other data is possible as well).
-The data is internally stored as a tree of named nodes and properties. Nodes
+                <p><p>Also referred to as Devicetree Blob (DTB). It is a flat binary encoding<br />
+of data (primarily devicetree data, although other data is possible as well).<br />
+The data is internally stored as a tree of named nodes and properties. Nodes<br />
 contain properties and child nodes, while properties are name-value pairs.</p>
-<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source
+<p>The Devicetree Blobs (<code>.dtb</code> files) are compiled from the Devicetree Source<br />
 files (<code>.dts</code>) through the Devicetree compiler (DTC).</p>
-<p>On Linux systems that support this, the blobs can be accessed in
+<p>On Linux systems that support this, the blobs can be accessed in<br />
 <code>/sys/firmware/fdt</code>:</p>
 <ul>
 <li><a href="https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw">https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw</a></li>
 </ul>
-<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is
+<p>The encoding of strings used in the <code>strings_block</code> and <code>structure_block</code> is<br />
 actually a subset of ASCII:</p>
 <p><a href="https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names">https://devicetree-specification.readthedocs.io/en/v0.3/devicetree-basics.html#node-names</a></p>
 <p>Example files:</p>
@@ -586,7 +586,7 @@ <h3>dtb.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/cpp_stl_11.html b/dune_2_pak/cpp_stl_11.html
index d5008ca47..f4509f78a 100644
--- a/dune_2_pak/cpp_stl_11.html
+++ b/dune_2_pak/cpp_stl_11.html
@@ -636,7 +636,7 @@ <h3>dune_2_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/cpp_stl_98.html b/dune_2_pak/cpp_stl_98.html
index 01992f947..790ee1395 100644
--- a/dune_2_pak/cpp_stl_98.html
+++ b/dune_2_pak/cpp_stl_98.html
@@ -668,7 +668,7 @@ <h3>dune_2_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/csharp.html b/dune_2_pak/csharp.html
index f1d881121..4b851f682 100644
--- a/dune_2_pak/csharp.html
+++ b/dune_2_pak/csharp.html
@@ -466,7 +466,7 @@ <h3>Dune2Pak.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/go.html b/dune_2_pak/go.html
index f2e3e1504..de6109a56 100644
--- a/dune_2_pak/go.html
+++ b/dune_2_pak/go.html
@@ -476,7 +476,7 @@ <h3>dune_2_pak.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/index.html b/dune_2_pak/index.html
index 27b2886a7..cb80d132c 100644
--- a/dune_2_pak/index.html
+++ b/dune_2_pak/index.html
@@ -290,7 +290,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/java.html b/dune_2_pak/java.html
index 02644563f..40308db47 100644
--- a/dune_2_pak/java.html
+++ b/dune_2_pak/java.html
@@ -461,7 +461,7 @@ <h3>Dune2Pak.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/javascript.html b/dune_2_pak/javascript.html
index 96f088e6c..d0cc5b04c 100644
--- a/dune_2_pak/javascript.html
+++ b/dune_2_pak/javascript.html
@@ -414,7 +414,7 @@ <h3>Dune2Pak.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/lua.html b/dune_2_pak/lua.html
index 9837b55b1..ff288dedc 100644
--- a/dune_2_pak/lua.html
+++ b/dune_2_pak/lua.html
@@ -374,7 +374,7 @@ <h3>dune_2_pak.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/nim.html b/dune_2_pak/nim.html
index af6ec3d9b..fa61cac3b 100644
--- a/dune_2_pak/nim.html
+++ b/dune_2_pak/nim.html
@@ -391,7 +391,7 @@ <h3>dune_2_pak.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/perl.html b/dune_2_pak/perl.html
index c43e38e0b..8bb836d4c 100644
--- a/dune_2_pak/perl.html
+++ b/dune_2_pak/perl.html
@@ -444,7 +444,7 @@ <h3>Dune2Pak.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/php.html b/dune_2_pak/php.html
index 4625e0bfc..6e8f457ba 100644
--- a/dune_2_pak/php.html
+++ b/dune_2_pak/php.html
@@ -363,7 +363,7 @@ <h3>Dune2Pak.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/python.html b/dune_2_pak/python.html
index c73e8d0e3..263ee4ebd 100644
--- a/dune_2_pak/python.html
+++ b/dune_2_pak/python.html
@@ -402,7 +402,7 @@ <h3>dune_2_pak.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/dune_2_pak/ruby.html b/dune_2_pak/ruby.html
index 194f3fb26..df0cc3a3b 100644
--- a/dune_2_pak/ruby.html
+++ b/dune_2_pak/ruby.html
@@ -394,7 +394,7 @@ <h3>dune_2_pak.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/csharp.html b/edid/csharp.html
index 54731c1f0..2180fec21 100644
--- a/edid/csharp.html
+++ b/edid/csharp.html
@@ -1188,7 +1188,7 @@ <h3>Edid.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/go.html b/edid/go.html
index d10299ca8..fe8b3d244 100644
--- a/edid/go.html
+++ b/edid/go.html
@@ -1258,7 +1258,7 @@ <h3>edid.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/index.html b/edid/index.html
index 0bd7ebebe..da07791de 100644
--- a/edid/index.html
+++ b/edid/index.html
@@ -509,7 +509,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/java.html b/edid/java.html
index 18737f0a1..ecaea1446 100644
--- a/edid/java.html
+++ b/edid/java.html
@@ -1060,7 +1060,7 @@ <h3>Edid.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/javascript.html b/edid/javascript.html
index da9577d1e..6402427e5 100644
--- a/edid/javascript.html
+++ b/edid/javascript.html
@@ -896,7 +896,7 @@ <h3>Edid.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/nim.html b/edid/nim.html
index afb92bb78..37969c4df 100644
--- a/edid/nim.html
+++ b/edid/nim.html
@@ -1031,7 +1031,7 @@ <h3>edid.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/perl.html b/edid/perl.html
index b51041e50..1b28c0292 100644
--- a/edid/perl.html
+++ b/edid/perl.html
@@ -912,7 +912,7 @@ <h3>Edid.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/php.html b/edid/php.html
index 5524ad1f8..be0d74b8e 100644
--- a/edid/php.html
+++ b/edid/php.html
@@ -917,7 +917,7 @@ <h3>Edid.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/python.html b/edid/python.html
index b64a5e4a4..253abc909 100644
--- a/edid/python.html
+++ b/edid/python.html
@@ -641,7 +641,7 @@ <h3>edid.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/edid/ruby.html b/edid/ruby.html
index 4c5d76c00..8131f0ff6 100644
--- a/edid/ruby.html
+++ b/edid/ruby.html
@@ -790,7 +790,7 @@ <h3>edid.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/cpp_stl_11.html b/efivar_signature_list/cpp_stl_11.html
index e3e94e23d..32ab5cdee 100644
--- a/efivar_signature_list/cpp_stl_11.html
+++ b/efivar_signature_list/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -985,7 +985,7 @@ <h3>efivar_signature_list.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/cpp_stl_98.html b/efivar_signature_list/cpp_stl_98.html
index 80d306ced..34a2e6b57 100644
--- a/efivar_signature_list/cpp_stl_98.html
+++ b/efivar_signature_list/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -1035,7 +1035,7 @@ <h3>efivar_signature_list.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/csharp.html b/efivar_signature_list/csharp.html
index 6cee1b10e..d5714e7b8 100644
--- a/efivar_signature_list/csharp.html
+++ b/efivar_signature_list/csharp.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -830,7 +830,7 @@ <h3>EfivarSignatureList.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/go.html b/efivar_signature_list/go.html
index 0560d4f90..78498936b 100644
--- a/efivar_signature_list/go.html
+++ b/efivar_signature_list/go.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -760,7 +760,7 @@ <h3>efivar_signature_list.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/graphviz.html b/efivar_signature_list/graphviz.html
index 5fe3952ba..f880d2184 100644
--- a/efivar_signature_list/graphviz.html
+++ b/efivar_signature_list/graphviz.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -410,7 +410,7 @@ <h3>efivar_signature_list.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/index.html b/efivar_signature_list/index.html
index e36bcf190..cda516c01 100644
--- a/efivar_signature_list/index.html
+++ b/efivar_signature_list/index.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -420,7 +420,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/java.html b/efivar_signature_list/java.html
index 5bf2c8212..1667ffbbe 100644
--- a/efivar_signature_list/java.html
+++ b/efivar_signature_list/java.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -747,7 +747,7 @@ <h3>EfivarSignatureList.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/javascript.html b/efivar_signature_list/javascript.html
index d60148f82..94083a894 100644
--- a/efivar_signature_list/javascript.html
+++ b/efivar_signature_list/javascript.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -655,7 +655,7 @@ <h3>EfivarSignatureList.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/lua.html b/efivar_signature_list/lua.html
index 870cc7031..35a9d15a4 100644
--- a/efivar_signature_list/lua.html
+++ b/efivar_signature_list/lua.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -579,7 +579,7 @@ <h3>efivar_signature_list.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/nim.html b/efivar_signature_list/nim.html
index ee4eeecdf..b7e6105c2 100644
--- a/efivar_signature_list/nim.html
+++ b/efivar_signature_list/nim.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -689,7 +689,7 @@ <h3>efivar_signature_list.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/perl.html b/efivar_signature_list/perl.html
index 840f48e04..481146aab 100644
--- a/efivar_signature_list/perl.html
+++ b/efivar_signature_list/perl.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -637,7 +637,7 @@ <h3>EfivarSignatureList.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/php.html b/efivar_signature_list/php.html
index 18515d083..3833ef0ec 100644
--- a/efivar_signature_list/php.html
+++ b/efivar_signature_list/php.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -604,7 +604,7 @@ <h3>EfivarSignatureList.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/python.html b/efivar_signature_list/python.html
index 9d32359b4..6fab4c9e1 100644
--- a/efivar_signature_list/python.html
+++ b/efivar_signature_list/python.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -595,7 +595,7 @@ <h3>efivar_signature_list.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/efivar_signature_list/ruby.html b/efivar_signature_list/ruby.html
index 0df77c87e..45658fd0e 100644
--- a/efivar_signature_list/ruby.html
+++ b/efivar_signature_list/ruby.html
@@ -105,16 +105,16 @@ <h1>UEFI Variable with Signature List:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and
-hashes. On a Linux system using UEFI, these variables are readable from
-/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,
-/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,
-/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and
-/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.
-(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as
-EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;
-as EFI_GLOBAL_VARIABLE).
-Each file contains an EFI attribute (32-bit integer) followed by a list of
+                <p><p>Parse UEFI variables db and dbx that contain signatures, certificates and<br />
+hashes. On a Linux system using UEFI, these variables are readable from<br />
+/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f,<br />
+/sys/firmware/efi/efivars/dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c,<br />
+/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f and<br />
+/sys/firmware/efi/efivars/dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c.<br />
+(&quot;d719b2cb-3d3a-4596-a3bc-dad00e67656f&quot; is defined as<br />
+EFI_IMAGE_SECURITY_DATABASE_GUID and &quot;8be4df61-93ca-11d2-aa0d-00e098032b8c&quot;<br />
+as EFI_GLOBAL_VARIABLE).<br />
+Each file contains an EFI attribute (32-bit integer) followed by a list of<br />
 EFI_SIGNATURE_LIST structures.</p>
 </p>
             </div>
@@ -592,7 +592,7 @@ <h3>efivar_signature_list.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/cpp_stl_11.html b/elf/cpp_stl_11.html
index e6aa7e9c0..93c122088 100644
--- a/elf/cpp_stl_11.html
+++ b/elf/cpp_stl_11.html
@@ -4821,7 +4821,7 @@ <h3>elf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/cpp_stl_98.html b/elf/cpp_stl_98.html
index 730f424a0..407ae9078 100644
--- a/elf/cpp_stl_98.html
+++ b/elf/cpp_stl_98.html
@@ -5009,7 +5009,7 @@ <h3>elf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/csharp.html b/elf/csharp.html
index ed7f61201..1b4185ee1 100644
--- a/elf/csharp.html
+++ b/elf/csharp.html
@@ -3724,7 +3724,7 @@ <h3>Elf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/graphviz.html b/elf/graphviz.html
index 4571400ac..a6e539690 100644
--- a/elf/graphviz.html
+++ b/elf/graphviz.html
@@ -1056,7 +1056,7 @@ <h3>elf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/index.html b/elf/index.html
index d26f3c467..31b583f56 100644
--- a/elf/index.html
+++ b/elf/index.html
@@ -2170,7 +2170,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/java.html b/elf/java.html
index ca0349c15..f27d64bdb 100644
--- a/elf/java.html
+++ b/elf/java.html
@@ -3500,7 +3500,7 @@ <h3>Elf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/javascript.html b/elf/javascript.html
index 0f1822650..574762aa0 100644
--- a/elf/javascript.html
+++ b/elf/javascript.html
@@ -3272,7 +3272,7 @@ <h3>Elf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/lua.html b/elf/lua.html
index c23b27bdf..cbf55bedb 100644
--- a/elf/lua.html
+++ b/elf/lua.html
@@ -2715,7 +2715,7 @@ <h3>elf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/nim.html b/elf/nim.html
index e6901ff08..5245bb674 100644
--- a/elf/nim.html
+++ b/elf/nim.html
@@ -3142,7 +3142,7 @@ <h3>elf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/perl.html b/elf/perl.html
index f0795f258..a15603f49 100644
--- a/elf/perl.html
+++ b/elf/perl.html
@@ -3082,7 +3082,7 @@ <h3>Elf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/php.html b/elf/php.html
index a9c908373..251bbbe12 100644
--- a/elf/php.html
+++ b/elf/php.html
@@ -3793,7 +3793,7 @@ <h3>Elf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/python.html b/elf/python.html
index 26b777a4f..3a44a6450 100644
--- a/elf/python.html
+++ b/elf/python.html
@@ -2406,7 +2406,7 @@ <h3>elf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/elf/ruby.html b/elf/ruby.html
index fc062e0ff..d3797bdc4 100644
--- a/elf/ruby.html
+++ b/elf/ruby.html
@@ -2466,7 +2466,7 @@ <h3>elf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/cpp_stl_11.html b/ethernet_frame/cpp_stl_11.html
index fe79b58f9..a2d51bf16 100644
--- a/ethernet_frame/cpp_stl_11.html
+++ b/ethernet_frame/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -630,7 +630,7 @@ <h3>ethernet_frame.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/cpp_stl_98.html b/ethernet_frame/cpp_stl_98.html
index d906b339b..88ff6ccf7 100644
--- a/ethernet_frame/cpp_stl_98.html
+++ b/ethernet_frame/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -653,7 +653,7 @@ <h3>ethernet_frame.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/csharp.html b/ethernet_frame/csharp.html
index 2aa54a426..d185c6c89 100644
--- a/ethernet_frame/csharp.html
+++ b/ethernet_frame/csharp.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -497,7 +497,7 @@ <h3>EthernetFrame.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/go.html b/ethernet_frame/go.html
index 438b0d0c1..bc58c8707 100644
--- a/ethernet_frame/go.html
+++ b/ethernet_frame/go.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -491,7 +491,7 @@ <h3>ethernet_frame.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/graphviz.html b/ethernet_frame/graphviz.html
index 18e57a596..2059149c2 100644
--- a/ethernet_frame/graphviz.html
+++ b/ethernet_frame/graphviz.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -322,7 +322,7 @@ <h3>ethernet_frame.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/index.html b/ethernet_frame/index.html
index 0c7ebf6b1..5028170c9 100644
--- a/ethernet_frame/index.html
+++ b/ethernet_frame/index.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -348,7 +348,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/java.html b/ethernet_frame/java.html
index e0b575664..468a6261c 100644
--- a/ethernet_frame/java.html
+++ b/ethernet_frame/java.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -518,7 +518,7 @@ <h3>EthernetFrame.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/javascript.html b/ethernet_frame/javascript.html
index 6cc4b8bb1..4bab5aa6d 100644
--- a/ethernet_frame/javascript.html
+++ b/ethernet_frame/javascript.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -463,7 +463,7 @@ <h3>EthernetFrame.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/lua.html b/ethernet_frame/lua.html
index 4e042c0d6..80c54390f 100644
--- a/ethernet_frame/lua.html
+++ b/ethernet_frame/lua.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -388,7 +388,7 @@ <h3>ethernet_frame.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/nim.html b/ethernet_frame/nim.html
index 5d0c28a4a..7cdff5262 100644
--- a/ethernet_frame/nim.html
+++ b/ethernet_frame/nim.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -435,7 +435,7 @@ <h3>ethernet_frame.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/perl.html b/ethernet_frame/perl.html
index c72779521..3cec3d8f8 100644
--- a/ethernet_frame/perl.html
+++ b/ethernet_frame/perl.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>EthernetFrame.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/php.html b/ethernet_frame/php.html
index ddff2bf2a..4086e54fc 100644
--- a/ethernet_frame/php.html
+++ b/ethernet_frame/php.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -416,7 +416,7 @@ <h3>EthernetFrame.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/python.html b/ethernet_frame/python.html
index 6df15d3b8..eda8d1d07 100644
--- a/ethernet_frame/python.html
+++ b/ethernet_frame/python.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -411,7 +411,7 @@ <h3>ethernet_frame.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ethernet_frame/ruby.html b/ethernet_frame/ruby.html
index af0717d3a..e4ea9ddc6 100644
--- a/ethernet_frame/ruby.html
+++ b/ethernet_frame/ruby.html
@@ -105,8 +105,8 @@ <h1>Ethernet frame (layer 2, IEEE 802.3):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit
-for Ethernet networks. In practice, many other networks and/or
+                <p><p>Ethernet frame is a OSI data link layer (layer 2) protocol data unit<br />
+for Ethernet networks. In practice, many other networks and/or<br />
 in-file dumps adopted the same format for encapsulation purposes.</p>
 </p>
             </div>
@@ -440,7 +440,7 @@ <h3>ethernet_frame.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/cpp_stl_11.html b/exif/cpp_stl_11.html
index 59ffc93fc..bc63db13a 100644
--- a/exif/cpp_stl_11.html
+++ b/exif/cpp_stl_11.html
@@ -1284,7 +1284,7 @@ <h3>exif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/cpp_stl_98.html b/exif/cpp_stl_98.html
index 89938b96f..62b88924e 100644
--- a/exif/cpp_stl_98.html
+++ b/exif/cpp_stl_98.html
@@ -1325,7 +1325,7 @@ <h3>exif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/csharp.html b/exif/csharp.html
index 328948580..b621c5af2 100644
--- a/exif/csharp.html
+++ b/exif/csharp.html
@@ -1097,7 +1097,7 @@ <h3>Exif.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/go.html b/exif/go.html
index 09b6a146b..ff40e30f5 100644
--- a/exif/go.html
+++ b/exif/go.html
@@ -1191,7 +1191,7 @@ <h3>exif.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/graphviz.html b/exif/graphviz.html
index acc2fd75d..ac2a0948b 100644
--- a/exif/graphviz.html
+++ b/exif/graphviz.html
@@ -358,7 +358,7 @@ <h3>exif.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/index.html b/exif/index.html
index 7c27266c5..773b32a7c 100644
--- a/exif/index.html
+++ b/exif/index.html
@@ -803,7 +803,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/java.html b/exif/java.html
index f47ce2a33..b8652230b 100644
--- a/exif/java.html
+++ b/exif/java.html
@@ -1072,7 +1072,7 @@ <h3>Exif.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/javascript.html b/exif/javascript.html
index c40a238bf..1336ecd25 100644
--- a/exif/javascript.html
+++ b/exif/javascript.html
@@ -1465,7 +1465,7 @@ <h3>Exif.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/lua.html b/exif/lua.html
index 99ee486d4..3d6b75178 100644
--- a/exif/lua.html
+++ b/exif/lua.html
@@ -965,7 +965,7 @@ <h3>exif.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/nim.html b/exif/nim.html
index 69730e99a..4749ddd1b 100644
--- a/exif/nim.html
+++ b/exif/nim.html
@@ -996,7 +996,7 @@ <h3>exif.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/perl.html b/exif/perl.html
index a0d1e8c9f..6a07817cf 100644
--- a/exif/perl.html
+++ b/exif/perl.html
@@ -1086,7 +1086,7 @@ <h3>Exif.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/php.html b/exif/php.html
index c628b9015..539759807 100644
--- a/exif/php.html
+++ b/exif/php.html
@@ -974,7 +974,7 @@ <h3>Exif.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/python.html b/exif/python.html
index 2833f75d0..29492a791 100644
--- a/exif/python.html
+++ b/exif/python.html
@@ -967,7 +967,7 @@ <h3>exif.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/exif/ruby.html b/exif/ruby.html
index 928715841..3f47e387d 100644
--- a/exif/ruby.html
+++ b/exif/ruby.html
@@ -985,7 +985,7 @@ <h3>exif.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/cpp_stl_11.html b/ext2/cpp_stl_11.html
index 7311a4796..6bbaa3337 100644
--- a/ext2/cpp_stl_11.html
+++ b/ext2/cpp_stl_11.html
@@ -1232,7 +1232,7 @@ <h3>ext2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/cpp_stl_98.html b/ext2/cpp_stl_98.html
index 1ec80a542..e00e32725 100644
--- a/ext2/cpp_stl_98.html
+++ b/ext2/cpp_stl_98.html
@@ -1333,7 +1333,7 @@ <h3>ext2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/csharp.html b/ext2/csharp.html
index 4afc348da..2d8237387 100644
--- a/ext2/csharp.html
+++ b/ext2/csharp.html
@@ -966,7 +966,7 @@ <h3>Ext2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/go.html b/ext2/go.html
index e0f773e32..4f0d08b16 100644
--- a/ext2/go.html
+++ b/ext2/go.html
@@ -1295,7 +1295,7 @@ <h3>ext2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/graphviz.html b/ext2/graphviz.html
index f8c4ee3ce..1206ba431 100644
--- a/ext2/graphviz.html
+++ b/ext2/graphviz.html
@@ -500,7 +500,7 @@ <h3>ext2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/index.html b/ext2/index.html
index c502d2e56..2845a27c3 100644
--- a/ext2/index.html
+++ b/ext2/index.html
@@ -527,7 +527,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/java.html b/ext2/java.html
index 4c0445d6b..52755badc 100644
--- a/ext2/java.html
+++ b/ext2/java.html
@@ -972,7 +972,7 @@ <h3>Ext2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/javascript.html b/ext2/javascript.html
index 1a04ef46e..d1812cae9 100644
--- a/ext2/javascript.html
+++ b/ext2/javascript.html
@@ -687,7 +687,7 @@ <h3>Ext2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/lua.html b/ext2/lua.html
index 4d5065d1a..9248295cb 100644
--- a/ext2/lua.html
+++ b/ext2/lua.html
@@ -639,7 +639,7 @@ <h3>ext2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/nim.html b/ext2/nim.html
index a6a162f21..ebe433e0f 100644
--- a/ext2/nim.html
+++ b/ext2/nim.html
@@ -811,7 +811,7 @@ <h3>ext2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/perl.html b/ext2/perl.html
index d1af47f30..65894856d 100644
--- a/ext2/perl.html
+++ b/ext2/perl.html
@@ -1183,7 +1183,7 @@ <h3>Ext2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/php.html b/ext2/php.html
index e590561dd..7e16f8190 100644
--- a/ext2/php.html
+++ b/ext2/php.html
@@ -768,7 +768,7 @@ <h3>Ext2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/python.html b/ext2/python.html
index 7ec3f6adf..111a21148 100644
--- a/ext2/python.html
+++ b/ext2/python.html
@@ -633,7 +633,7 @@ <h3>ext2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ext2/ruby.html b/ext2/ruby.html
index c9d7aa91d..39d077d05 100644
--- a/ext2/ruby.html
+++ b/ext2/ruby.html
@@ -687,7 +687,7 @@ <h3>ext2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/cpp_stl_11.html b/fallout2_dat/cpp_stl_11.html
index bd63c5157..6b501137f 100644
--- a/fallout2_dat/cpp_stl_11.html
+++ b/fallout2_dat/cpp_stl_11.html
@@ -777,7 +777,7 @@ <h3>fallout2_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/cpp_stl_98.html b/fallout2_dat/cpp_stl_98.html
index 03ad50538..4a7f2d5b9 100644
--- a/fallout2_dat/cpp_stl_98.html
+++ b/fallout2_dat/cpp_stl_98.html
@@ -824,7 +824,7 @@ <h3>fallout2_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/csharp.html b/fallout2_dat/csharp.html
index f0ffe8749..1ef05b110 100644
--- a/fallout2_dat/csharp.html
+++ b/fallout2_dat/csharp.html
@@ -573,7 +573,7 @@ <h3>Fallout2Dat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/go.html b/fallout2_dat/go.html
index 2ff92083b..665e6b053 100644
--- a/fallout2_dat/go.html
+++ b/fallout2_dat/go.html
@@ -615,7 +615,7 @@ <h3>fallout2_dat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/graphviz.html b/fallout2_dat/graphviz.html
index abb0084ea..6c230b6e6 100644
--- a/fallout2_dat/graphviz.html
+++ b/fallout2_dat/graphviz.html
@@ -373,7 +373,7 @@ <h3>fallout2_dat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/index.html b/fallout2_dat/index.html
index 5a2caeb4f..02b5cd293 100644
--- a/fallout2_dat/index.html
+++ b/fallout2_dat/index.html
@@ -340,7 +340,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/java.html b/fallout2_dat/java.html
index 04c7075a7..96ec890b6 100644
--- a/fallout2_dat/java.html
+++ b/fallout2_dat/java.html
@@ -577,7 +577,7 @@ <h3>Fallout2Dat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/javascript.html b/fallout2_dat/javascript.html
index 64937502e..27d083eec 100644
--- a/fallout2_dat/javascript.html
+++ b/fallout2_dat/javascript.html
@@ -487,7 +487,7 @@ <h3>Fallout2Dat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/lua.html b/fallout2_dat/lua.html
index f91dca21c..9224a871d 100644
--- a/fallout2_dat/lua.html
+++ b/fallout2_dat/lua.html
@@ -446,7 +446,7 @@ <h3>fallout2_dat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/nim.html b/fallout2_dat/nim.html
index 2135ff82a..bdc95bc96 100644
--- a/fallout2_dat/nim.html
+++ b/fallout2_dat/nim.html
@@ -476,7 +476,7 @@ <h3>fallout2_dat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/perl.html b/fallout2_dat/perl.html
index bee60dc7a..11e002208 100644
--- a/fallout2_dat/perl.html
+++ b/fallout2_dat/perl.html
@@ -586,7 +586,7 @@ <h3>Fallout2Dat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/php.html b/fallout2_dat/php.html
index 728951591..99963acb6 100644
--- a/fallout2_dat/php.html
+++ b/fallout2_dat/php.html
@@ -447,7 +447,7 @@ <h3>Fallout2Dat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/python.html b/fallout2_dat/python.html
index b1f3e0166..05908cf61 100644
--- a/fallout2_dat/python.html
+++ b/fallout2_dat/python.html
@@ -466,7 +466,7 @@ <h3>fallout2_dat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout2_dat/ruby.html b/fallout2_dat/ruby.html
index 2d6c40793..f4db68eb9 100644
--- a/fallout2_dat/ruby.html
+++ b/fallout2_dat/ruby.html
@@ -462,7 +462,7 @@ <h3>fallout2_dat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/cpp_stl_11.html b/fallout_dat/cpp_stl_11.html
index 4f975150f..f51219b54 100644
--- a/fallout_dat/cpp_stl_11.html
+++ b/fallout_dat/cpp_stl_11.html
@@ -645,7 +645,7 @@ <h3>fallout_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/cpp_stl_98.html b/fallout_dat/cpp_stl_98.html
index 8bd5a94f7..a4ae8de94 100644
--- a/fallout_dat/cpp_stl_98.html
+++ b/fallout_dat/cpp_stl_98.html
@@ -692,7 +692,7 @@ <h3>fallout_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/csharp.html b/fallout_dat/csharp.html
index bec96b76c..23bf317e5 100644
--- a/fallout_dat/csharp.html
+++ b/fallout_dat/csharp.html
@@ -506,7 +506,7 @@ <h3>FalloutDat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/go.html b/fallout_dat/go.html
index e9cc6119b..df58c7449 100644
--- a/fallout_dat/go.html
+++ b/fallout_dat/go.html
@@ -521,7 +521,7 @@ <h3>fallout_dat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/graphviz.html b/fallout_dat/graphviz.html
index 07d5450d5..1a38309ba 100644
--- a/fallout_dat/graphviz.html
+++ b/fallout_dat/graphviz.html
@@ -356,7 +356,7 @@ <h3>fallout_dat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/index.html b/fallout_dat/index.html
index 3437aafdd..b2da746ff 100644
--- a/fallout_dat/index.html
+++ b/fallout_dat/index.html
@@ -340,7 +340,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/java.html b/fallout_dat/java.html
index 6e5fe44cf..bb1a9ce60 100644
--- a/fallout_dat/java.html
+++ b/fallout_dat/java.html
@@ -531,7 +531,7 @@ <h3>FalloutDat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/javascript.html b/fallout_dat/javascript.html
index 0b20e2703..1bd9d5d25 100644
--- a/fallout_dat/javascript.html
+++ b/fallout_dat/javascript.html
@@ -437,7 +437,7 @@ <h3>FalloutDat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/lua.html b/fallout_dat/lua.html
index 40237fc8d..31eb44455 100644
--- a/fallout_dat/lua.html
+++ b/fallout_dat/lua.html
@@ -389,7 +389,7 @@ <h3>fallout_dat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/nim.html b/fallout_dat/nim.html
index 3976823ee..836457f14 100644
--- a/fallout_dat/nim.html
+++ b/fallout_dat/nim.html
@@ -424,7 +424,7 @@ <h3>fallout_dat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/perl.html b/fallout_dat/perl.html
index 7b13847b1..8997badf0 100644
--- a/fallout_dat/perl.html
+++ b/fallout_dat/perl.html
@@ -553,7 +553,7 @@ <h3>FalloutDat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/php.html b/fallout_dat/php.html
index 835102768..44ff5cf58 100644
--- a/fallout_dat/php.html
+++ b/fallout_dat/php.html
@@ -417,7 +417,7 @@ <h3>FalloutDat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/python.html b/fallout_dat/python.html
index da1f7f542..059ba36fd 100644
--- a/fallout_dat/python.html
+++ b/fallout_dat/python.html
@@ -417,7 +417,7 @@ <h3>fallout_dat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fallout_dat/ruby.html b/fallout_dat/ruby.html
index 7bed6dde3..ab6563b49 100644
--- a/fallout_dat/ruby.html
+++ b/fallout_dat/ruby.html
@@ -433,7 +433,7 @@ <h3>fallout_dat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/cpp_stl_11.html b/fasttracker_xm_module/cpp_stl_11.html
index b8710912a..2df074751 100644
--- a/fasttracker_xm_module/cpp_stl_11.html
+++ b/fasttracker_xm_module/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1500,7 +1500,7 @@ <h3>fasttracker_xm_module.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/cpp_stl_98.html b/fasttracker_xm_module/cpp_stl_98.html
index 69d4c5d7e..aeb09b3f4 100644
--- a/fasttracker_xm_module/cpp_stl_98.html
+++ b/fasttracker_xm_module/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1670,7 +1670,7 @@ <h3>fasttracker_xm_module.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/csharp.html b/fasttracker_xm_module/csharp.html
index f019bb1b6..7d1fb5d21 100644
--- a/fasttracker_xm_module/csharp.html
+++ b/fasttracker_xm_module/csharp.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1130,7 +1130,7 @@ <h3>FasttrackerXmModule.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/go.html b/fasttracker_xm_module/go.html
index e0160cfd8..14904ad56 100644
--- a/fasttracker_xm_module/go.html
+++ b/fasttracker_xm_module/go.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1292,7 +1292,7 @@ <h3>fasttracker_xm_module.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/graphviz.html b/fasttracker_xm_module/graphviz.html
index fc4b6c27f..d9d250395 100644
--- a/fasttracker_xm_module/graphviz.html
+++ b/fasttracker_xm_module/graphviz.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -539,7 +539,7 @@ <h3>fasttracker_xm_module.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/index.html b/fasttracker_xm_module/index.html
index a28bf12c1..b51bf8487 100644
--- a/fasttracker_xm_module/index.html
+++ b/fasttracker_xm_module/index.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -601,7 +601,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/java.html b/fasttracker_xm_module/java.html
index 7c39e20b8..3e3eccf2b 100644
--- a/fasttracker_xm_module/java.html
+++ b/fasttracker_xm_module/java.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1208,7 +1208,7 @@ <h3>FasttrackerXmModule.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/javascript.html b/fasttracker_xm_module/javascript.html
index 55c37488d..5e8cfe2be 100644
--- a/fasttracker_xm_module/javascript.html
+++ b/fasttracker_xm_module/javascript.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -854,7 +854,7 @@ <h3>FasttrackerXmModule.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/lua.html b/fasttracker_xm_module/lua.html
index b9e70f631..0aba5c1a0 100644
--- a/fasttracker_xm_module/lua.html
+++ b/fasttracker_xm_module/lua.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -733,7 +733,7 @@ <h3>fasttracker_xm_module.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/nim.html b/fasttracker_xm_module/nim.html
index c1280243c..23a4d35da 100644
--- a/fasttracker_xm_module/nim.html
+++ b/fasttracker_xm_module/nim.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -958,7 +958,7 @@ <h3>fasttracker_xm_module.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/perl.html b/fasttracker_xm_module/perl.html
index 665729b2e..f6b6f948e 100644
--- a/fasttracker_xm_module/perl.html
+++ b/fasttracker_xm_module/perl.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -1316,7 +1316,7 @@ <h3>FasttrackerXmModule.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/php.html b/fasttracker_xm_module/php.html
index 88f145db0..e8fef866b 100644
--- a/fasttracker_xm_module/php.html
+++ b/fasttracker_xm_module/php.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -932,7 +932,7 @@ <h3>FasttrackerXmModule.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/python.html b/fasttracker_xm_module/python.html
index a6e46f769..897522cd1 100644
--- a/fasttracker_xm_module/python.html
+++ b/fasttracker_xm_module/python.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -667,7 +667,7 @@ <h3>fasttracker_xm_module.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/fasttracker_xm_module/ruby.html b/fasttracker_xm_module/ruby.html
index 28562c72b..ba2294645 100644
--- a/fasttracker_xm_module/ruby.html
+++ b/fasttracker_xm_module/ruby.html
@@ -105,12 +105,12 @@ <h1>Extended Module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>XM (standing for eXtended Module) is a popular module music file
-format, that was introduced in 1994 in FastTracker2 by Triton demo
-group. Akin to MOD files, it bundles both digital samples
-(instruments) and instructions on which note to play at what time
-(patterns), which provides good audio quality with relatively small
-file size. Audio is reproducible without relying on the sound of
+                <p><p>XM (standing for eXtended Module) is a popular module music file<br />
+format, that was introduced in 1994 in FastTracker2 by Triton demo<br />
+group. Akin to MOD files, it bundles both digital samples<br />
+(instruments) and instructions on which note to play at what time<br />
+(patterns), which provides good audio quality with relatively small<br />
+file size. Audio is reproducible without relying on the sound of<br />
 particular hardware samplers or synths.</p>
 </p>
             </div>
@@ -825,7 +825,7 @@ <h3>fasttracker_xm_module.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/cpp_stl_11.html b/ftl_dat/cpp_stl_11.html
index 53551ecc7..fa93d79f0 100644
--- a/ftl_dat/cpp_stl_11.html
+++ b/ftl_dat/cpp_stl_11.html
@@ -547,7 +547,7 @@ <h3>ftl_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/cpp_stl_98.html b/ftl_dat/cpp_stl_98.html
index a7431922e..3b5b0112f 100644
--- a/ftl_dat/cpp_stl_98.html
+++ b/ftl_dat/cpp_stl_98.html
@@ -576,7 +576,7 @@ <h3>ftl_dat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/csharp.html b/ftl_dat/csharp.html
index f9b0a77eb..f30a17e19 100644
--- a/ftl_dat/csharp.html
+++ b/ftl_dat/csharp.html
@@ -419,7 +419,7 @@ <h3>FtlDat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/go.html b/ftl_dat/go.html
index 7369da511..7284dd16e 100644
--- a/ftl_dat/go.html
+++ b/ftl_dat/go.html
@@ -399,7 +399,7 @@ <h3>ftl_dat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/graphviz.html b/ftl_dat/graphviz.html
index 08e7394ed..f2a6f81f1 100644
--- a/ftl_dat/graphviz.html
+++ b/ftl_dat/graphviz.html
@@ -305,7 +305,7 @@ <h3>ftl_dat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/index.html b/ftl_dat/index.html
index e70c9b5cf..e161e0021 100644
--- a/ftl_dat/index.html
+++ b/ftl_dat/index.html
@@ -282,7 +282,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/java.html b/ftl_dat/java.html
index 917791b25..85e4c3831 100644
--- a/ftl_dat/java.html
+++ b/ftl_dat/java.html
@@ -430,7 +430,7 @@ <h3>FtlDat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/javascript.html b/ftl_dat/javascript.html
index 2fab88624..eb579dea2 100644
--- a/ftl_dat/javascript.html
+++ b/ftl_dat/javascript.html
@@ -379,7 +379,7 @@ <h3>FtlDat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/lua.html b/ftl_dat/lua.html
index 854285539..37b8ba135 100644
--- a/ftl_dat/lua.html
+++ b/ftl_dat/lua.html
@@ -331,7 +331,7 @@ <h3>ftl_dat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/nim.html b/ftl_dat/nim.html
index f0ff2c8fa..972c2b135 100644
--- a/ftl_dat/nim.html
+++ b/ftl_dat/nim.html
@@ -351,7 +351,7 @@ <h3>ftl_dat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/perl.html b/ftl_dat/perl.html
index af084542f..1299732a2 100644
--- a/ftl_dat/perl.html
+++ b/ftl_dat/perl.html
@@ -421,7 +421,7 @@ <h3>FtlDat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/php.html b/ftl_dat/php.html
index 183021a15..1457aa883 100644
--- a/ftl_dat/php.html
+++ b/ftl_dat/php.html
@@ -338,7 +338,7 @@ <h3>FtlDat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/python.html b/ftl_dat/python.html
index 1c011c9d5..d7060530d 100644
--- a/ftl_dat/python.html
+++ b/ftl_dat/python.html
@@ -362,7 +362,7 @@ <h3>ftl_dat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ftl_dat/ruby.html b/ftl_dat/ruby.html
index 6c44e8e3e..741f6573e 100644
--- a/ftl_dat/ruby.html
+++ b/ftl_dat/ruby.html
@@ -369,7 +369,7 @@ <h3>ftl_dat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/cpp_stl_11.html b/genmidi_op2/cpp_stl_11.html
index 978478694..df0fe429c 100644
--- a/genmidi_op2/cpp_stl_11.html
+++ b/genmidi_op2/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -684,7 +684,7 @@ <h3>genmidi_op2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/cpp_stl_98.html b/genmidi_op2/cpp_stl_98.html
index 5033d8be2..54f51df1e 100644
--- a/genmidi_op2/cpp_stl_98.html
+++ b/genmidi_op2/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -731,7 +731,7 @@ <h3>genmidi_op2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/csharp.html b/genmidi_op2/csharp.html
index c1cf985e5..e12341ebf 100644
--- a/genmidi_op2/csharp.html
+++ b/genmidi_op2/csharp.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -553,7 +553,7 @@ <h3>GenmidiOp2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/go.html b/genmidi_op2/go.html
index cad1b827c..a4dfe34ca 100644
--- a/genmidi_op2/go.html
+++ b/genmidi_op2/go.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -545,7 +545,7 @@ <h3>genmidi_op2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/graphviz.html b/genmidi_op2/graphviz.html
index 58f768f92..70c98010b 100644
--- a/genmidi_op2/graphviz.html
+++ b/genmidi_op2/graphviz.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -350,7 +350,7 @@ <h3>genmidi_op2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/index.html b/genmidi_op2/index.html
index 67b6c0bef..4983d938f 100644
--- a/genmidi_op2/index.html
+++ b/genmidi_op2/index.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -364,7 +364,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/java.html b/genmidi_op2/java.html
index f1ebba572..237034c8e 100644
--- a/genmidi_op2/java.html
+++ b/genmidi_op2/java.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -568,7 +568,7 @@ <h3>GenmidiOp2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/javascript.html b/genmidi_op2/javascript.html
index b1b52258c..9e4c65a9a 100644
--- a/genmidi_op2/javascript.html
+++ b/genmidi_op2/javascript.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -481,7 +481,7 @@ <h3>GenmidiOp2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/lua.html b/genmidi_op2/lua.html
index 84b049ff8..0211dee89 100644
--- a/genmidi_op2/lua.html
+++ b/genmidi_op2/lua.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -411,7 +411,7 @@ <h3>genmidi_op2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/nim.html b/genmidi_op2/nim.html
index 8c536ae41..360c26375 100644
--- a/genmidi_op2/nim.html
+++ b/genmidi_op2/nim.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -469,7 +469,7 @@ <h3>genmidi_op2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/perl.html b/genmidi_op2/perl.html
index bd664d952..ceb572817 100644
--- a/genmidi_op2/perl.html
+++ b/genmidi_op2/perl.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -545,7 +545,7 @@ <h3>GenmidiOp2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/php.html b/genmidi_op2/php.html
index 0eb84c180..8646901b0 100644
--- a/genmidi_op2/php.html
+++ b/genmidi_op2/php.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -460,7 +460,7 @@ <h3>GenmidiOp2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/python.html b/genmidi_op2/python.html
index 0898f231a..32bd207f6 100644
--- a/genmidi_op2/python.html
+++ b/genmidi_op2/python.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -431,7 +431,7 @@ <h3>genmidi_op2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/genmidi_op2/ruby.html b/genmidi_op2/ruby.html
index e6597d633..60ab59470 100644
--- a/genmidi_op2/ruby.html
+++ b/genmidi_op2/ruby.html
@@ -105,9 +105,9 @@ <h1>GENMIDI.OP2 OPL2 sound bank:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound
-library to play MIDI files with General MIDI instruments using OPL2
-sound chip (which was commonly installed on popular AdLib and Sound
+                <p><p>GENMIDI.OP2 is a sound bank file used by players based on DMX sound<br />
+library to play MIDI files with General MIDI instruments using OPL2<br />
+sound chip (which was commonly installed on popular AdLib and Sound<br />
 Blaster sound cards).</p>
 <p>Major users of DMX sound library include:</p>
 <ul>
@@ -469,7 +469,7 @@ <h3>genmidi_op2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/cpp_stl_11.html b/gettext_mo/cpp_stl_11.html
index 590d78aa9..096a9c7b7 100644
--- a/gettext_mo/cpp_stl_11.html
+++ b/gettext_mo/cpp_stl_11.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -1393,7 +1393,7 @@ <h3>gettext_mo.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/cpp_stl_98.html b/gettext_mo/cpp_stl_98.html
index d66321711..039cd97dd 100644
--- a/gettext_mo/cpp_stl_98.html
+++ b/gettext_mo/cpp_stl_98.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -1479,7 +1479,7 @@ <h3>gettext_mo.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/csharp.html b/gettext_mo/csharp.html
index a9a141fd9..719c68e5f 100644
--- a/gettext_mo/csharp.html
+++ b/gettext_mo/csharp.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -1052,7 +1052,7 @@ <h3>GettextMo.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/go.html b/gettext_mo/go.html
index d3e9f5245..febd3270d 100644
--- a/gettext_mo/go.html
+++ b/gettext_mo/go.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -1210,7 +1210,7 @@ <h3>gettext_mo.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/graphviz.html b/gettext_mo/graphviz.html
index 5512dbecc..9819e3111 100644
--- a/gettext_mo/graphviz.html
+++ b/gettext_mo/graphviz.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -501,7 +501,7 @@ <h3>gettext_mo.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/index.html b/gettext_mo/index.html
index 30f740a4f..717ef8fe7 100644
--- a/gettext_mo/index.html
+++ b/gettext_mo/index.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -486,7 +486,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/java.html b/gettext_mo/java.html
index ef8f4614c..254c492e1 100644
--- a/gettext_mo/java.html
+++ b/gettext_mo/java.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -919,7 +919,7 @@ <h3>GettextMo.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/javascript.html b/gettext_mo/javascript.html
index d8b009e86..311a192a7 100644
--- a/gettext_mo/javascript.html
+++ b/gettext_mo/javascript.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -830,7 +830,7 @@ <h3>GettextMo.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/lua.html b/gettext_mo/lua.html
index 0c5dd2ac0..59297be8b 100644
--- a/gettext_mo/lua.html
+++ b/gettext_mo/lua.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -817,7 +817,7 @@ <h3>gettext_mo.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/nim.html b/gettext_mo/nim.html
index a7a2eb60c..fb0d94cac 100644
--- a/gettext_mo/nim.html
+++ b/gettext_mo/nim.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -869,7 +869,7 @@ <h3>gettext_mo.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/perl.html b/gettext_mo/perl.html
index e2ce0ac94..6953e9a10 100644
--- a/gettext_mo/perl.html
+++ b/gettext_mo/perl.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -972,7 +972,7 @@ <h3>GettextMo.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/php.html b/gettext_mo/php.html
index ddc7e9fb4..f52bb5c67 100644
--- a/gettext_mo/php.html
+++ b/gettext_mo/php.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -799,7 +799,7 @@ <h3>GettextMo.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/python.html b/gettext_mo/python.html
index e31b628ee..19711ab44 100644
--- a/gettext_mo/python.html
+++ b/gettext_mo/python.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -769,7 +769,7 @@ <h3>gettext_mo.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gettext_mo/ruby.html b/gettext_mo/ruby.html
index 644224b90..213129817 100644
--- a/gettext_mo/ruby.html
+++ b/gettext_mo/ruby.html
@@ -105,17 +105,17 @@ <h1>gettext binary database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular
-solution in free/open source software world to do i18n/l10n of
-software, by providing translated strings that will substitute
+                <p><p><a href="https://www.gnu.org/software/gettext/">GNU gettext</a> is a popular<br />
+solution in free/open source software world to do i18n/l10n of<br />
+software, by providing translated strings that will substitute<br />
 strings in original language (typically, English).</p>
-<p>gettext .mo is a binary database format which stores these string
-translation pairs in an efficient binary format, ready to be used by
-gettext-enabled software. .mo format is a result of compilation of
-text-based .po files using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a>
-utility. The reverse conversion (.mo -&gt; .po) is also possible using
-<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a>
+<p>gettext .mo is a binary database format which stores these string<br />
+translation pairs in an efficient binary format, ready to be used by<br />
+gettext-enabled software. .mo format is a result of compilation of<br />
+text-based .po files using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgfmt-Invocation.html#msgfmt-Invocation">msgfmt</a><br />
+utility. The reverse conversion (.mo -&gt; .po) is also possible using<br />
+<a href="https://www.gnu.org/software/gettext/manual/html_node/msgunfmt-Invocation.html#msgunfmt-Invocation">msgunfmt</a><br />
 decompiler utility.</p>
 </p>
             </div>
@@ -765,7 +765,7 @@ <h3>gettext_mo.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/cpp_stl_11.html b/gif/cpp_stl_11.html
index 63118db0a..bc7fecf25 100644
--- a/gif/cpp_stl_11.html
+++ b/gif/cpp_stl_11.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1398,7 +1398,7 @@ <h3>gif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/cpp_stl_98.html b/gif/cpp_stl_98.html
index 0f63140cf..be6ddffdb 100644
--- a/gif/cpp_stl_98.html
+++ b/gif/cpp_stl_98.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1541,7 +1541,7 @@ <h3>gif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/csharp.html b/gif/csharp.html
index 82636d9a6..b05bc58ab 100644
--- a/gif/csharp.html
+++ b/gif/csharp.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1015,7 +1015,7 @@ <h3>Gif.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/go.html b/gif/go.html
index cace4d794..43822a76b 100644
--- a/gif/go.html
+++ b/gif/go.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1053,7 +1053,7 @@ <h3>gif.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/graphviz.html b/gif/graphviz.html
index 1acfefa40..ecf2a181a 100644
--- a/gif/graphviz.html
+++ b/gif/graphviz.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -531,7 +531,7 @@ <h3>gif.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/index.html b/gif/index.html
index bbb1a297a..85b277492 100644
--- a/gif/index.html
+++ b/gif/index.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -484,7 +484,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/java.html b/gif/java.html
index 9ff5dcbda..832b791a8 100644
--- a/gif/java.html
+++ b/gif/java.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1070,7 +1070,7 @@ <h3>Gif.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/javascript.html b/gif/javascript.html
index cc56e0c25..0f09d5793 100644
--- a/gif/javascript.html
+++ b/gif/javascript.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -770,7 +770,7 @@ <h3>Gif.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/lua.html b/gif/lua.html
index 9b30d0aa6..98d02b92e 100644
--- a/gif/lua.html
+++ b/gif/lua.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -710,7 +710,7 @@ <h3>gif.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/nim.html b/gif/nim.html
index 46a837672..c55c0e3ad 100644
--- a/gif/nim.html
+++ b/gif/nim.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -821,7 +821,7 @@ <h3>gif.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/perl.html b/gif/perl.html
index 623ed08a3..59db55cb8 100644
--- a/gif/perl.html
+++ b/gif/perl.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -1108,7 +1108,7 @@ <h3>Gif.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/php.html b/gif/php.html
index 940f42034..8d408da47 100644
--- a/gif/php.html
+++ b/gif/php.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -743,7 +743,7 @@ <h3>Gif.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/python.html b/gif/python.html
index 80c755fd4..fea0288a6 100644
--- a/gif/python.html
+++ b/gif/python.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -689,7 +689,7 @@ <h3>gif.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gif/ruby.html b/gif/ruby.html
index df8e5481a..cd48d4073 100644
--- a/gif/ruby.html
+++ b/gif/ruby.html
@@ -105,19 +105,19 @@ <h1>GIF (Graphics Interchange Format) image file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIF (Graphics Interchange Format) is an image file format, developed
-in 1987. It became popular in 1990s as one of the main image formats
+                <p><p>GIF (Graphics Interchange Format) is an image file format, developed<br />
+in 1987. It became popular in 1990s as one of the main image formats<br />
 used in World Wide Web.</p>
-<p>GIF format allows encoding of palette-based images up to 256 colors
-(each of the colors can be chosen from a 24-bit RGB
-colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless
+<p>GIF format allows encoding of palette-based images up to 256 colors<br />
+(each of the colors can be chosen from a 24-bit RGB<br />
+colorspace). Image data stream uses LZW (Lempel-Ziv-Welch) lossless<br />
 compression.</p>
-<p>Over the years, several version of the format were published and
-several extensions to it were made, namely, a popular Netscape
-extension that allows to store several images in one file, switching
+<p>Over the years, several version of the format were published and<br />
+several extensions to it were made, namely, a popular Netscape<br />
+extension that allows to store several images in one file, switching<br />
 between them, which produces crude form of animation.</p>
-<p>Structurally, format consists of several mandatory headers and then
-a stream of blocks follows. Blocks can carry additional
+<p>Structurally, format consists of several mandatory headers and then<br />
+a stream of blocks follows. Blocks can carry additional<br />
 metainformation or image data.</p>
 </p>
             </div>
@@ -705,7 +705,7 @@ <h3>gif.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/cpp_stl_11.html b/gimp_brush/cpp_stl_11.html
index 488446c05..fb507aeca 100644
--- a/gimp_brush/cpp_stl_11.html
+++ b/gimp_brush/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -867,7 +867,7 @@ <h3>gimp_brush.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/cpp_stl_98.html b/gimp_brush/cpp_stl_98.html
index ccf86c85e..79a17fb35 100644
--- a/gimp_brush/cpp_stl_98.html
+++ b/gimp_brush/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -923,7 +923,7 @@ <h3>gimp_brush.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/csharp.html b/gimp_brush/csharp.html
index eeaf636fd..ebc692c0f 100644
--- a/gimp_brush/csharp.html
+++ b/gimp_brush/csharp.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -691,7 +691,7 @@ <h3>GimpBrush.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/go.html b/gimp_brush/go.html
index d9e2883ab..67cdee0dc 100644
--- a/gimp_brush/go.html
+++ b/gimp_brush/go.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -665,7 +665,7 @@ <h3>gimp_brush.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/graphviz.html b/gimp_brush/graphviz.html
index e954b3e81..7694b16df 100644
--- a/gimp_brush/graphviz.html
+++ b/gimp_brush/graphviz.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -411,7 +411,7 @@ <h3>gimp_brush.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/index.html b/gimp_brush/index.html
index 49f659d26..17a1e0932 100644
--- a/gimp_brush/index.html
+++ b/gimp_brush/index.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -408,7 +408,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/java.html b/gimp_brush/java.html
index f6d9802f1..eab28d1cf 100644
--- a/gimp_brush/java.html
+++ b/gimp_brush/java.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -691,7 +691,7 @@ <h3>GimpBrush.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/javascript.html b/gimp_brush/javascript.html
index 5912e5e61..1967ac399 100644
--- a/gimp_brush/javascript.html
+++ b/gimp_brush/javascript.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -567,7 +567,7 @@ <h3>GimpBrush.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/lua.html b/gimp_brush/lua.html
index 0d38cb2aa..01775d126 100644
--- a/gimp_brush/lua.html
+++ b/gimp_brush/lua.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -517,7 +517,7 @@ <h3>gimp_brush.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/nim.html b/gimp_brush/nim.html
index ef8beede6..e6af7f451 100644
--- a/gimp_brush/nim.html
+++ b/gimp_brush/nim.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -553,7 +553,7 @@ <h3>gimp_brush.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/perl.html b/gimp_brush/perl.html
index 67f412714..a545c18b9 100644
--- a/gimp_brush/perl.html
+++ b/gimp_brush/perl.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -661,7 +661,7 @@ <h3>GimpBrush.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/php.html b/gimp_brush/php.html
index d33208585..33a076db2 100644
--- a/gimp_brush/php.html
+++ b/gimp_brush/php.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -524,7 +524,7 @@ <h3>GimpBrush.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/python.html b/gimp_brush/python.html
index 0a9686b0b..c25ba6b02 100644
--- a/gimp_brush/python.html
+++ b/gimp_brush/python.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -517,7 +517,7 @@ <h3>gimp_brush.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gimp_brush/ruby.html b/gimp_brush/ruby.html
index 7035701d2..764d74979 100644
--- a/gimp_brush/ruby.html
+++ b/gimp_brush/ruby.html
@@ -105,14 +105,14 @@ <h1>GIMP brush file version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.
-It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,
-for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move
-the tool. The Spacing parameter sets the distance between the brush marks as a percentage
+                <p><p>GIMP brush format is native to the GIMP image editor for storing a brush or a texture.<br />
+It can be used in all <a href="https://docs.gimp.org/2.10/en/gimp-tools-paint.html">Paint Tools</a>,<br />
+for example Pencil and Paintbrush. It works by repeating the brush bitmap as you move<br />
+the tool. The Spacing parameter sets the distance between the brush marks as a percentage<br />
 of brush width. Its default value can be set in the brush file.</p>
-<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded
-into GIMP for use in the paint tools by copying them into one of the Brush Folders -
-select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section
+<p>You can also use GIMP to create new brushes in this format. Custom brushes can be loaded<br />
+into GIMP for use in the paint tools by copying them into one of the Brush Folders -<br />
+select <strong>Edit</strong> &gt; <strong>Preferences</strong> in the menu bar, expand the <strong>Folders</strong> section<br />
 and choose <strong>Brushes</strong> to see the recognized Brush Folders or to add new ones.</p>
 </p>
             </div>
@@ -521,7 +521,7 @@ <h3>gimp_brush.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/cpp_stl_11.html b/glibc_utmp/cpp_stl_11.html
index da7e0ec65..b29e21236 100644
--- a/glibc_utmp/cpp_stl_11.html
+++ b/glibc_utmp/cpp_stl_11.html
@@ -618,7 +618,7 @@ <h3>glibc_utmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/cpp_stl_98.html b/glibc_utmp/cpp_stl_98.html
index 8f1ffe450..dfe44e11e 100644
--- a/glibc_utmp/cpp_stl_98.html
+++ b/glibc_utmp/cpp_stl_98.html
@@ -656,7 +656,7 @@ <h3>glibc_utmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/csharp.html b/glibc_utmp/csharp.html
index 4cf07b2db..e7b679d3b 100644
--- a/glibc_utmp/csharp.html
+++ b/glibc_utmp/csharp.html
@@ -497,7 +497,7 @@ <h3>GlibcUtmp.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/go.html b/glibc_utmp/go.html
index cdd9f492d..1e9b54087 100644
--- a/glibc_utmp/go.html
+++ b/glibc_utmp/go.html
@@ -498,7 +498,7 @@ <h3>glibc_utmp.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/graphviz.html b/glibc_utmp/graphviz.html
index b1706f393..26c090800 100644
--- a/glibc_utmp/graphviz.html
+++ b/glibc_utmp/graphviz.html
@@ -314,7 +314,7 @@ <h3>glibc_utmp.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/index.html b/glibc_utmp/index.html
index 99baf59e6..96f7ff48d 100644
--- a/glibc_utmp/index.html
+++ b/glibc_utmp/index.html
@@ -335,7 +335,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/java.html b/glibc_utmp/java.html
index 1aac5c860..560b2b76f 100644
--- a/glibc_utmp/java.html
+++ b/glibc_utmp/java.html
@@ -527,7 +527,7 @@ <h3>GlibcUtmp.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/javascript.html b/glibc_utmp/javascript.html
index 136d3b005..cf9e25568 100644
--- a/glibc_utmp/javascript.html
+++ b/glibc_utmp/javascript.html
@@ -456,7 +456,7 @@ <h3>GlibcUtmp.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/lua.html b/glibc_utmp/lua.html
index 21a90094a..f8158c295 100644
--- a/glibc_utmp/lua.html
+++ b/glibc_utmp/lua.html
@@ -376,7 +376,7 @@ <h3>glibc_utmp.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/nim.html b/glibc_utmp/nim.html
index 9f9eee336..d610d5c66 100644
--- a/glibc_utmp/nim.html
+++ b/glibc_utmp/nim.html
@@ -429,7 +429,7 @@ <h3>glibc_utmp.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/perl.html b/glibc_utmp/perl.html
index 963a6b207..697109301 100644
--- a/glibc_utmp/perl.html
+++ b/glibc_utmp/perl.html
@@ -479,7 +479,7 @@ <h3>GlibcUtmp.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/php.html b/glibc_utmp/php.html
index f078a515a..5f997a5c4 100644
--- a/glibc_utmp/php.html
+++ b/glibc_utmp/php.html
@@ -422,7 +422,7 @@ <h3>GlibcUtmp.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/python.html b/glibc_utmp/python.html
index 401f21f37..2012c392a 100644
--- a/glibc_utmp/python.html
+++ b/glibc_utmp/python.html
@@ -384,7 +384,7 @@ <h3>glibc_utmp.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/glibc_utmp/ruby.html b/glibc_utmp/ruby.html
index 06cce23c3..d2dfe7a34 100644
--- a/glibc_utmp/ruby.html
+++ b/glibc_utmp/ruby.html
@@ -436,7 +436,7 @@ <h3>glibc_utmp.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/cpp_stl_11.html b/gltf_binary/cpp_stl_11.html
index 0aa327487..704b6dfd6 100644
--- a/gltf_binary/cpp_stl_11.html
+++ b/gltf_binary/cpp_stl_11.html
@@ -681,7 +681,7 @@ <h3>gltf_binary.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/cpp_stl_98.html b/gltf_binary/cpp_stl_98.html
index a0031d35a..25033e044 100644
--- a/gltf_binary/cpp_stl_98.html
+++ b/gltf_binary/cpp_stl_98.html
@@ -728,7 +728,7 @@ <h3>gltf_binary.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/csharp.html b/gltf_binary/csharp.html
index 23896ab4e..e3734c59e 100644
--- a/gltf_binary/csharp.html
+++ b/gltf_binary/csharp.html
@@ -518,7 +518,7 @@ <h3>GltfBinary.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/go.html b/gltf_binary/go.html
index 718291784..ba44204c0 100644
--- a/gltf_binary/go.html
+++ b/gltf_binary/go.html
@@ -504,7 +504,7 @@ <h3>gltf_binary.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/graphviz.html b/gltf_binary/graphviz.html
index be5d377f7..96f670754 100644
--- a/gltf_binary/graphviz.html
+++ b/gltf_binary/graphviz.html
@@ -343,7 +343,7 @@ <h3>gltf_binary.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/index.html b/gltf_binary/index.html
index 9648197b9..f0beb75d3 100644
--- a/gltf_binary/index.html
+++ b/gltf_binary/index.html
@@ -336,7 +336,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/java.html b/gltf_binary/java.html
index d8178936b..b6caf4c0f 100644
--- a/gltf_binary/java.html
+++ b/gltf_binary/java.html
@@ -563,7 +563,7 @@ <h3>GltfBinary.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/javascript.html b/gltf_binary/javascript.html
index 858332d99..bf4c95151 100644
--- a/gltf_binary/javascript.html
+++ b/gltf_binary/javascript.html
@@ -457,7 +457,7 @@ <h3>GltfBinary.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/lua.html b/gltf_binary/lua.html
index fc833e1b2..4799ed292 100644
--- a/gltf_binary/lua.html
+++ b/gltf_binary/lua.html
@@ -395,7 +395,7 @@ <h3>gltf_binary.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/nim.html b/gltf_binary/nim.html
index 90b266c92..24005ed26 100644
--- a/gltf_binary/nim.html
+++ b/gltf_binary/nim.html
@@ -433,7 +433,7 @@ <h3>gltf_binary.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/perl.html b/gltf_binary/perl.html
index c083afc3c..f877705f3 100644
--- a/gltf_binary/perl.html
+++ b/gltf_binary/perl.html
@@ -529,7 +529,7 @@ <h3>GltfBinary.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/php.html b/gltf_binary/php.html
index a225570f7..ae145716b 100644
--- a/gltf_binary/php.html
+++ b/gltf_binary/php.html
@@ -418,7 +418,7 @@ <h3>GltfBinary.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/python.html b/gltf_binary/python.html
index 1ab9b39b7..b30d956de 100644
--- a/gltf_binary/python.html
+++ b/gltf_binary/python.html
@@ -414,7 +414,7 @@ <h3>gltf_binary.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gltf_binary/ruby.html b/gltf_binary/ruby.html
index 28e69253d..f65d81a7d 100644
--- a/gltf_binary/ruby.html
+++ b/gltf_binary/ruby.html
@@ -436,7 +436,7 @@ <h3>gltf_binary.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/csharp.html b/google_protobuf/csharp.html
index e3cd6feaa..6c8b7be22 100644
--- a/google_protobuf/csharp.html
+++ b/google_protobuf/csharp.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -549,7 +549,7 @@ <h3>GoogleProtobuf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/go.html b/google_protobuf/go.html
index 92e91502a..7bf3034dd 100644
--- a/google_protobuf/go.html
+++ b/google_protobuf/go.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -525,7 +525,7 @@ <h3>google_protobuf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/graphviz.html b/google_protobuf/graphviz.html
index 50d8006d1..89a87e926 100644
--- a/google_protobuf/graphviz.html
+++ b/google_protobuf/graphviz.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -347,7 +347,7 @@ <h3>google_protobuf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/index.html b/google_protobuf/index.html
index bb4a3c0ab..31608fda9 100644
--- a/google_protobuf/index.html
+++ b/google_protobuf/index.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -376,7 +376,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/java.html b/google_protobuf/java.html
index c7825c36f..e3443e7e2 100644
--- a/google_protobuf/java.html
+++ b/google_protobuf/java.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -568,7 +568,7 @@ <h3>GoogleProtobuf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/javascript.html b/google_protobuf/javascript.html
index 08d310fa9..fb96a76ce 100644
--- a/google_protobuf/javascript.html
+++ b/google_protobuf/javascript.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -506,7 +506,7 @@ <h3>GoogleProtobuf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/lua.html b/google_protobuf/lua.html
index f8884cc36..ae529f4fd 100644
--- a/google_protobuf/lua.html
+++ b/google_protobuf/lua.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -438,7 +438,7 @@ <h3>google_protobuf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/nim.html b/google_protobuf/nim.html
index b01feb3d9..158d024c8 100644
--- a/google_protobuf/nim.html
+++ b/google_protobuf/nim.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -476,7 +476,7 @@ <h3>google_protobuf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/perl.html b/google_protobuf/perl.html
index 005876937..774a76723 100644
--- a/google_protobuf/perl.html
+++ b/google_protobuf/perl.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -460,7 +460,7 @@ <h3>GoogleProtobuf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/php.html b/google_protobuf/php.html
index 88234f961..6f12bd898 100644
--- a/google_protobuf/php.html
+++ b/google_protobuf/php.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -453,7 +453,7 @@ <h3>GoogleProtobuf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/python.html b/google_protobuf/python.html
index e110980f3..798c9a0e4 100644
--- a/google_protobuf/python.html
+++ b/google_protobuf/python.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -457,7 +457,7 @@ <h3>google_protobuf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/google_protobuf/ruby.html b/google_protobuf/ruby.html
index b1e6443de..431471443 100644
--- a/google_protobuf/ruby.html
+++ b/google_protobuf/ruby.html
@@ -105,31 +105,31 @@ <h1>Google Protocol Buffers (protobuf):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data
-serialization scheme used for communication protocols, data storage,
-etc. There are implementations are available for almost every
-popular language. The focus points of this scheme are brevity (data
-is encoded in a very size-efficient manner) and extensibility (one
-can add keys to the structure, while keeping it readable in previous
+                <p><p>Google Protocol Buffers (AKA protobuf) is a popular data<br />
+serialization scheme used for communication protocols, data storage,<br />
+etc. There are implementations are available for almost every<br />
+popular language. The focus points of this scheme are brevity (data<br />
+is encoded in a very size-efficient manner) and extensibility (one<br />
+can add keys to the structure, while keeping it readable in previous<br />
 version of software).</p>
-<p>Protobuf uses semi-self-describing encoding scheme for its
-messages. It means that it is possible to parse overall structure of
-the message (skipping over fields one can't understand), but to
-fully understand the message, one needs a protocol definition file
+<p>Protobuf uses semi-self-describing encoding scheme for its<br />
+messages. It means that it is possible to parse overall structure of<br />
+the message (skipping over fields one can't understand), but to<br />
+fully understand the message, one needs a protocol definition file<br />
 (<code>.proto</code>). To be specific:</p>
 <ul>
-<li>&quot;Keys&quot; in key-value pairs provided in the message are identified
-only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on
+<li>&quot;Keys&quot; in key-value pairs provided in the message are identified<br />
+only with an integer &quot;field tag&quot;. <code>.proto</code> file provides info on<br />
 which symbolic field names these field tags map to.</li>
-<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data
-type in its common sense (i.e. you can't, for example, distinguish
-<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but
-it's enough information to determine how many bytes to
-parse. Interpretation of the value should be done according to the
+<li>&quot;Keys&quot; also provide something called &quot;wire type&quot;. It's not a data<br />
+type in its common sense (i.e. you can't, for example, distinguish<br />
+<code>sint32</code> vs <code>uint32</code> vs some enum, or <code>string</code> from <code>bytes</code>), but<br />
+it's enough information to determine how many bytes to<br />
+parse. Interpretation of the value should be done according to the<br />
 type specified in <code>.proto</code> file.</li>
-<li>There's no direct information on which fields are optional /
-required, which fields may be repeated or constitute a map, what
-restrictions are placed on fields usage in a single message, what
+<li>There's no direct information on which fields are optional /<br />
+required, which fields may be repeated or constitute a map, what<br />
+restrictions are placed on fields usage in a single message, what<br />
 are the fields' default values, etc, etc.</li>
 </ul>
 </p>
@@ -475,7 +475,7 @@ <h3>google_protobuf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/cpp_stl_11.html b/gpt_partition_table/cpp_stl_11.html
index 828be6c5b..821260794 100644
--- a/gpt_partition_table/cpp_stl_11.html
+++ b/gpt_partition_table/cpp_stl_11.html
@@ -663,7 +663,7 @@ <h3>gpt_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/cpp_stl_98.html b/gpt_partition_table/cpp_stl_98.html
index 8b7386069..174f8d91f 100644
--- a/gpt_partition_table/cpp_stl_98.html
+++ b/gpt_partition_table/cpp_stl_98.html
@@ -704,7 +704,7 @@ <h3>gpt_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/csharp.html b/gpt_partition_table/csharp.html
index acdea1d2d..2da7796f3 100644
--- a/gpt_partition_table/csharp.html
+++ b/gpt_partition_table/csharp.html
@@ -526,7 +526,7 @@ <h3>GptPartitionTable.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/go.html b/gpt_partition_table/go.html
index d6fdc78bc..8d6c8082c 100644
--- a/gpt_partition_table/go.html
+++ b/gpt_partition_table/go.html
@@ -589,7 +589,7 @@ <h3>gpt_partition_table.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/graphviz.html b/gpt_partition_table/graphviz.html
index 5320f08af..43428305e 100644
--- a/gpt_partition_table/graphviz.html
+++ b/gpt_partition_table/graphviz.html
@@ -343,7 +343,7 @@ <h3>gpt_partition_table.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/index.html b/gpt_partition_table/index.html
index 805cda787..a3d1ec7f5 100644
--- a/gpt_partition_table/index.html
+++ b/gpt_partition_table/index.html
@@ -335,7 +335,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/java.html b/gpt_partition_table/java.html
index 6c52eb6e4..401fca925 100644
--- a/gpt_partition_table/java.html
+++ b/gpt_partition_table/java.html
@@ -517,7 +517,7 @@ <h3>GptPartitionTable.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/javascript.html b/gpt_partition_table/javascript.html
index 7f535f9c1..b75e05999 100644
--- a/gpt_partition_table/javascript.html
+++ b/gpt_partition_table/javascript.html
@@ -439,7 +439,7 @@ <h3>GptPartitionTable.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/lua.html b/gpt_partition_table/lua.html
index 5f620ee75..5c708e255 100644
--- a/gpt_partition_table/lua.html
+++ b/gpt_partition_table/lua.html
@@ -398,7 +398,7 @@ <h3>gpt_partition_table.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/nim.html b/gpt_partition_table/nim.html
index 0a11b8a78..159a108aa 100644
--- a/gpt_partition_table/nim.html
+++ b/gpt_partition_table/nim.html
@@ -445,7 +445,7 @@ <h3>gpt_partition_table.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/perl.html b/gpt_partition_table/perl.html
index edfd43e59..49c67361f 100644
--- a/gpt_partition_table/perl.html
+++ b/gpt_partition_table/perl.html
@@ -545,7 +545,7 @@ <h3>GptPartitionTable.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/php.html b/gpt_partition_table/php.html
index 3ada8e792..3b7a834a8 100644
--- a/gpt_partition_table/php.html
+++ b/gpt_partition_table/php.html
@@ -419,7 +419,7 @@ <h3>GptPartitionTable.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/python.html b/gpt_partition_table/python.html
index 4c4e12a64..cded2809d 100644
--- a/gpt_partition_table/python.html
+++ b/gpt_partition_table/python.html
@@ -427,7 +427,7 @@ <h3>gpt_partition_table.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gpt_partition_table/ruby.html b/gpt_partition_table/ruby.html
index e185a89ba..bd71ad0c7 100644
--- a/gpt_partition_table/ruby.html
+++ b/gpt_partition_table/ruby.html
@@ -432,7 +432,7 @@ <h3>gpt_partition_table.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/cpp_stl_11.html b/gran_turismo_vol/cpp_stl_11.html
index 598ef6fd4..fae01b77a 100644
--- a/gran_turismo_vol/cpp_stl_11.html
+++ b/gran_turismo_vol/cpp_stl_11.html
@@ -623,7 +623,7 @@ <h3>gran_turismo_vol.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/cpp_stl_98.html b/gran_turismo_vol/cpp_stl_98.html
index fdf652321..529b31bef 100644
--- a/gran_turismo_vol/cpp_stl_98.html
+++ b/gran_turismo_vol/cpp_stl_98.html
@@ -646,7 +646,7 @@ <h3>gran_turismo_vol.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/csharp.html b/gran_turismo_vol/csharp.html
index 01a91d5e7..53c38ab5f 100644
--- a/gran_turismo_vol/csharp.html
+++ b/gran_turismo_vol/csharp.html
@@ -502,7 +502,7 @@ <h3>GranTurismoVol.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/go.html b/gran_turismo_vol/go.html
index f5c2d9e9f..358f7e403 100644
--- a/gran_turismo_vol/go.html
+++ b/gran_turismo_vol/go.html
@@ -497,7 +497,7 @@ <h3>gran_turismo_vol.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/graphviz.html b/gran_turismo_vol/graphviz.html
index 5c147adb8..8e7e7c3d8 100644
--- a/gran_turismo_vol/graphviz.html
+++ b/gran_turismo_vol/graphviz.html
@@ -345,7 +345,7 @@ <h3>gran_turismo_vol.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/index.html b/gran_turismo_vol/index.html
index 8128f830c..4b66761be 100644
--- a/gran_turismo_vol/index.html
+++ b/gran_turismo_vol/index.html
@@ -318,7 +318,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/java.html b/gran_turismo_vol/java.html
index 7506f75ab..80e760a7f 100644
--- a/gran_turismo_vol/java.html
+++ b/gran_turismo_vol/java.html
@@ -475,7 +475,7 @@ <h3>GranTurismoVol.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/javascript.html b/gran_turismo_vol/javascript.html
index 6888a4ffc..0226d23a6 100644
--- a/gran_turismo_vol/javascript.html
+++ b/gran_turismo_vol/javascript.html
@@ -432,7 +432,7 @@ <h3>GranTurismoVol.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/lua.html b/gran_turismo_vol/lua.html
index 68bde14c6..bb92b7baf 100644
--- a/gran_turismo_vol/lua.html
+++ b/gran_turismo_vol/lua.html
@@ -397,7 +397,7 @@ <h3>gran_turismo_vol.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/nim.html b/gran_turismo_vol/nim.html
index 19eccc547..d63002629 100644
--- a/gran_turismo_vol/nim.html
+++ b/gran_turismo_vol/nim.html
@@ -414,7 +414,7 @@ <h3>gran_turismo_vol.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/perl.html b/gran_turismo_vol/perl.html
index 32e491a9b..5b48cbb78 100644
--- a/gran_turismo_vol/perl.html
+++ b/gran_turismo_vol/perl.html
@@ -460,7 +460,7 @@ <h3>GranTurismoVol.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/php.html b/gran_turismo_vol/php.html
index e7caba603..d70800e09 100644
--- a/gran_turismo_vol/php.html
+++ b/gran_turismo_vol/php.html
@@ -393,7 +393,7 @@ <h3>GranTurismoVol.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/python.html b/gran_turismo_vol/python.html
index b1b944787..185d44d9d 100644
--- a/gran_turismo_vol/python.html
+++ b/gran_turismo_vol/python.html
@@ -422,7 +422,7 @@ <h3>gran_turismo_vol.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gran_turismo_vol/ruby.html b/gran_turismo_vol/ruby.html
index 9c198ac3e..561f3a3b1 100644
--- a/gran_turismo_vol/ruby.html
+++ b/gran_turismo_vol/ruby.html
@@ -410,7 +410,7 @@ <h3>gran_turismo_vol.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/cpp_stl_11.html b/grub2_font/cpp_stl_11.html
index 29f4ce56b..73ebb22e4 100644
--- a/grub2_font/cpp_stl_11.html
+++ b/grub2_font/cpp_stl_11.html
@@ -1183,7 +1183,7 @@ <h3>grub2_font.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/cpp_stl_98.html b/grub2_font/cpp_stl_98.html
index 8daaadac7..2d52df27a 100644
--- a/grub2_font/cpp_stl_98.html
+++ b/grub2_font/cpp_stl_98.html
@@ -1290,7 +1290,7 @@ <h3>grub2_font.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/csharp.html b/grub2_font/csharp.html
index 64969bbe9..9edb0fe38 100644
--- a/grub2_font/csharp.html
+++ b/grub2_font/csharp.html
@@ -846,7 +846,7 @@ <h3>Grub2Font.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/go.html b/grub2_font/go.html
index 5360c79f9..105d4d32c 100644
--- a/grub2_font/go.html
+++ b/grub2_font/go.html
@@ -908,7 +908,7 @@ <h3>grub2_font.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/graphviz.html b/grub2_font/graphviz.html
index 4cfa0eb7a..796c45ef8 100644
--- a/grub2_font/graphviz.html
+++ b/grub2_font/graphviz.html
@@ -462,7 +462,7 @@ <h3>grub2_font.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/index.html b/grub2_font/index.html
index 57df2d5f3..df5f90089 100644
--- a/grub2_font/index.html
+++ b/grub2_font/index.html
@@ -408,7 +408,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/java.html b/grub2_font/java.html
index 3f818bbae..db91f3932 100644
--- a/grub2_font/java.html
+++ b/grub2_font/java.html
@@ -911,7 +911,7 @@ <h3>Grub2Font.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/javascript.html b/grub2_font/javascript.html
index b58199871..61f9b0092 100644
--- a/grub2_font/javascript.html
+++ b/grub2_font/javascript.html
@@ -675,7 +675,7 @@ <h3>Grub2Font.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/lua.html b/grub2_font/lua.html
index 3a80646f1..4e64359c1 100644
--- a/grub2_font/lua.html
+++ b/grub2_font/lua.html
@@ -598,7 +598,7 @@ <h3>grub2_font.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/nim.html b/grub2_font/nim.html
index 78c251f2c..118800d1d 100644
--- a/grub2_font/nim.html
+++ b/grub2_font/nim.html
@@ -700,7 +700,7 @@ <h3>grub2_font.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/perl.html b/grub2_font/perl.html
index 693e57bcc..fd2e178b7 100644
--- a/grub2_font/perl.html
+++ b/grub2_font/perl.html
@@ -962,7 +962,7 @@ <h3>Grub2Font.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/php.html b/grub2_font/php.html
index 9a4ea0090..5ee1d822c 100644
--- a/grub2_font/php.html
+++ b/grub2_font/php.html
@@ -643,7 +643,7 @@ <h3>Grub2Font.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/python.html b/grub2_font/python.html
index 55367ced7..68cd10bff 100644
--- a/grub2_font/python.html
+++ b/grub2_font/python.html
@@ -576,7 +576,7 @@ <h3>grub2_font.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/grub2_font/ruby.html b/grub2_font/ruby.html
index 5117fc38f..6f6860950 100644
--- a/grub2_font/ruby.html
+++ b/grub2_font/ruby.html
@@ -622,7 +622,7 @@ <h3>grub2_font.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/cpp_stl_11.html b/gzip/cpp_stl_11.html
index 85df9a1a5..2f0f8e1d0 100644
--- a/gzip/cpp_stl_11.html
+++ b/gzip/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -892,7 +892,7 @@ <h3>gzip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/cpp_stl_98.html b/gzip/cpp_stl_98.html
index 1741b5549..936b01abe 100644
--- a/gzip/cpp_stl_98.html
+++ b/gzip/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -951,7 +951,7 @@ <h3>gzip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/csharp.html b/gzip/csharp.html
index 28bfde18c..db52a0ff5 100644
--- a/gzip/csharp.html
+++ b/gzip/csharp.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -672,7 +672,7 @@ <h3>Gzip.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/go.html b/gzip/go.html
index a066c0ea3..ff15e5d63 100644
--- a/gzip/go.html
+++ b/gzip/go.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -700,7 +700,7 @@ <h3>gzip.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/graphviz.html b/gzip/graphviz.html
index e0584b151..9d9d8169e 100644
--- a/gzip/graphviz.html
+++ b/gzip/graphviz.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -375,7 +375,7 @@ <h3>gzip.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/index.html b/gzip/index.html
index 8054017f2..e2c605e1e 100644
--- a/gzip/index.html
+++ b/gzip/index.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -467,7 +467,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/java.html b/gzip/java.html
index 14b3e6c4c..65e25d2de 100644
--- a/gzip/java.html
+++ b/gzip/java.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -737,7 +737,7 @@ <h3>Gzip.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/javascript.html b/gzip/javascript.html
index 3d82a8e82..4ad349f83 100644
--- a/gzip/javascript.html
+++ b/gzip/javascript.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -590,7 +590,7 @@ <h3>Gzip.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/lua.html b/gzip/lua.html
index 0b5a636c3..b9f48e263 100644
--- a/gzip/lua.html
+++ b/gzip/lua.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -489,7 +489,7 @@ <h3>gzip.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/nim.html b/gzip/nim.html
index af038c7bc..0cd5e7fdc 100644
--- a/gzip/nim.html
+++ b/gzip/nim.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -577,7 +577,7 @@ <h3>gzip.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/perl.html b/gzip/perl.html
index be43ca534..76c80f0dd 100644
--- a/gzip/perl.html
+++ b/gzip/perl.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -680,7 +680,7 @@ <h3>Gzip.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/php.html b/gzip/php.html
index fb5e293a2..1f1c887b3 100644
--- a/gzip/php.html
+++ b/gzip/php.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -622,7 +622,7 @@ <h3>Gzip.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/python.html b/gzip/python.html
index 28b6be54b..30ea5617c 100644
--- a/gzip/python.html
+++ b/gzip/python.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -487,7 +487,7 @@ <h3>gzip.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/gzip/ruby.html b/gzip/ruby.html
index 0bb5fdfb4..fa8ca6e12 100644
--- a/gzip/ruby.html
+++ b/gzip/ruby.html
@@ -105,12 +105,12 @@ <h1>.gz file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Gzip is a popular and standard single-file archiving format. It
-essentially provides a container that stores original file name,
-timestamp and a few other things (like optional comment), basic
+                <p><p>Gzip is a popular and standard single-file archiving format. It<br />
+essentially provides a container that stores original file name,<br />
+timestamp and a few other things (like optional comment), basic<br />
 CRCs, etc, and a file compressed by a chosen compression algorithm.</p>
-<p>As of 2019, there is actually only one working solution for
-compression algorithms, so it's typically raw DEFLATE stream
+<p>As of 2019, there is actually only one working solution for<br />
+compression algorithms, so it's typically raw DEFLATE stream<br />
 (without zlib header) in all gzipped files.</p>
 </p>
             </div>
@@ -557,7 +557,7 @@ <h3>gzip.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/cpp_stl_11.html b/hashcat_restore/cpp_stl_11.html
index f0bc1ceb7..07bd95e43 100644
--- a/hashcat_restore/cpp_stl_11.html
+++ b/hashcat_restore/cpp_stl_11.html
@@ -436,7 +436,7 @@ <h3>hashcat_restore.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/cpp_stl_98.html b/hashcat_restore/cpp_stl_98.html
index 9c06c3cdc..42415a0d6 100644
--- a/hashcat_restore/cpp_stl_98.html
+++ b/hashcat_restore/cpp_stl_98.html
@@ -447,7 +447,7 @@ <h3>hashcat_restore.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/csharp.html b/hashcat_restore/csharp.html
index b4e91fc0f..04a231bd6 100644
--- a/hashcat_restore/csharp.html
+++ b/hashcat_restore/csharp.html
@@ -357,7 +357,7 @@ <h3>HashcatRestore.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/go.html b/hashcat_restore/go.html
index 6fdf9572c..3b74a3c7f 100644
--- a/hashcat_restore/go.html
+++ b/hashcat_restore/go.html
@@ -337,7 +337,7 @@ <h3>hashcat_restore.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/graphviz.html b/hashcat_restore/graphviz.html
index 03e6c743e..1077b985a 100644
--- a/hashcat_restore/graphviz.html
+++ b/hashcat_restore/graphviz.html
@@ -275,7 +275,7 @@ <h3>hashcat_restore.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/index.html b/hashcat_restore/index.html
index 21a359ae9..c1270fea8 100644
--- a/hashcat_restore/index.html
+++ b/hashcat_restore/index.html
@@ -271,7 +271,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/java.html b/hashcat_restore/java.html
index 1af4d34cc..7d74fffda 100644
--- a/hashcat_restore/java.html
+++ b/hashcat_restore/java.html
@@ -365,7 +365,7 @@ <h3>HashcatRestore.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/javascript.html b/hashcat_restore/javascript.html
index 73ec9d4c5..2b28056b4 100644
--- a/hashcat_restore/javascript.html
+++ b/hashcat_restore/javascript.html
@@ -333,7 +333,7 @@ <h3>HashcatRestore.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/lua.html b/hashcat_restore/lua.html
index 319b3214e..dac0d774a 100644
--- a/hashcat_restore/lua.html
+++ b/hashcat_restore/lua.html
@@ -285,7 +285,7 @@ <h3>hashcat_restore.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/nim.html b/hashcat_restore/nim.html
index 22c47cb59..e84ac7561 100644
--- a/hashcat_restore/nim.html
+++ b/hashcat_restore/nim.html
@@ -305,7 +305,7 @@ <h3>hashcat_restore.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/perl.html b/hashcat_restore/perl.html
index 0bfa4c86a..990779bd3 100644
--- a/hashcat_restore/perl.html
+++ b/hashcat_restore/perl.html
@@ -350,7 +350,7 @@ <h3>HashcatRestore.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/php.html b/hashcat_restore/php.html
index f6a5f5ba2..24a89183d 100644
--- a/hashcat_restore/php.html
+++ b/hashcat_restore/php.html
@@ -297,7 +297,7 @@ <h3>HashcatRestore.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/python.html b/hashcat_restore/python.html
index fa389c4e9..3b0ae03fe 100644
--- a/hashcat_restore/python.html
+++ b/hashcat_restore/python.html
@@ -328,7 +328,7 @@ <h3>hashcat_restore.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hashcat_restore/ruby.html b/hashcat_restore/ruby.html
index 0e71be41c..62dce54b0 100644
--- a/hashcat_restore/ruby.html
+++ b/hashcat_restore/ruby.html
@@ -336,7 +336,7 @@ <h3>hashcat_restore.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/cpp_stl_11.html b/hccap/cpp_stl_11.html
index 2e715b330..4bcd4e4a4 100644
--- a/hccap/cpp_stl_11.html
+++ b/hccap/cpp_stl_11.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -598,7 +598,7 @@ <h3>hccap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/cpp_stl_98.html b/hccap/cpp_stl_98.html
index cd24b2fc0..c1e80d36a 100644
--- a/hccap/cpp_stl_98.html
+++ b/hccap/cpp_stl_98.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -630,7 +630,7 @@ <h3>hccap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/csharp.html b/hccap/csharp.html
index 02c90cb8d..e0abaa811 100644
--- a/hccap/csharp.html
+++ b/hccap/csharp.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -477,7 +477,7 @@ <h3>Hccap.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/go.html b/hccap/go.html
index 1a7853ac6..6eb1e9aed 100644
--- a/hccap/go.html
+++ b/hccap/go.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -477,7 +477,7 @@ <h3>hccap.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/graphviz.html b/hccap/graphviz.html
index 02d688c72..f68046d5e 100644
--- a/hccap/graphviz.html
+++ b/hccap/graphviz.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -308,7 +308,7 @@ <h3>hccap.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/index.html b/hccap/index.html
index e8e40e0b1..0ce84e549 100644
--- a/hccap/index.html
+++ b/hccap/index.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -314,7 +314,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/java.html b/hccap/java.html
index cef5e0dba..4a7568463 100644
--- a/hccap/java.html
+++ b/hccap/java.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -486,7 +486,7 @@ <h3>Hccap.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/javascript.html b/hccap/javascript.html
index 3e4f29a13..694c711f9 100644
--- a/hccap/javascript.html
+++ b/hccap/javascript.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -426,7 +426,7 @@ <h3>Hccap.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/lua.html b/hccap/lua.html
index 77557aeb3..d05208c38 100644
--- a/hccap/lua.html
+++ b/hccap/lua.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -362,7 +362,7 @@ <h3>hccap.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/nim.html b/hccap/nim.html
index 6bdf6b12a..92e5c2f81 100644
--- a/hccap/nim.html
+++ b/hccap/nim.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -411,7 +411,7 @@ <h3>hccap.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/perl.html b/hccap/perl.html
index c17f90012..448812f61 100644
--- a/hccap/perl.html
+++ b/hccap/perl.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -446,7 +446,7 @@ <h3>Hccap.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/php.html b/hccap/php.html
index ae4756750..45f8cb66c 100644
--- a/hccap/php.html
+++ b/hccap/php.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -391,7 +391,7 @@ <h3>Hccap.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/python.html b/hccap/python.html
index 0e0f747e4..001ca3abc 100644
--- a/hccap/python.html
+++ b/hccap/python.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -380,7 +380,7 @@ <h3>hccap.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccap/ruby.html b/hccap/ruby.html
index 7a6e2fb8a..2426b02cf 100644
--- a/hccap/ruby.html
+++ b/hccap/ruby.html
@@ -106,7 +106,7 @@ <h1>Hashcat capture file (old version):
         <div class="row">
             <div class="col-md-8">
                 <p><p>Native format of Hashcat password &quot;recovery&quot; utility.</p>
-<p>A sample of file for testing can be downloaded from
+<p>A sample of file for testing can be downloaded from<br />
 <a href="https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap">https://web.archive.org/web/20150220013635if_/http://hashcat.net:80/misc/example_hashes/hashcat.hccap</a></p>
 </p>
             </div>
@@ -412,7 +412,7 @@ <h3>hccap.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/cpp_stl_11.html b/hccapx/cpp_stl_11.html
index 1d6aa7b84..51c41cee0 100644
--- a/hccapx/cpp_stl_11.html
+++ b/hccapx/cpp_stl_11.html
@@ -585,7 +585,7 @@ <h3>hccapx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/cpp_stl_98.html b/hccapx/cpp_stl_98.html
index 4609e0628..cf62738a9 100644
--- a/hccapx/cpp_stl_98.html
+++ b/hccapx/cpp_stl_98.html
@@ -605,7 +605,7 @@ <h3>hccapx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/csharp.html b/hccapx/csharp.html
index a1da5daa9..a4d69df5a 100644
--- a/hccapx/csharp.html
+++ b/hccapx/csharp.html
@@ -490,7 +490,7 @@ <h3>Hccapx.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/go.html b/hccapx/go.html
index d345622ad..7ff0e53e1 100644
--- a/hccapx/go.html
+++ b/hccapx/go.html
@@ -501,7 +501,7 @@ <h3>hccapx.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/graphviz.html b/hccapx/graphviz.html
index c935305f2..22ffe6159 100644
--- a/hccapx/graphviz.html
+++ b/hccapx/graphviz.html
@@ -303,7 +303,7 @@ <h3>hccapx.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/index.html b/hccapx/index.html
index ceb5abf67..2f85ddc0a 100644
--- a/hccapx/index.html
+++ b/hccapx/index.html
@@ -345,7 +345,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/java.html b/hccapx/java.html
index e2d7dea4d..756d99543 100644
--- a/hccapx/java.html
+++ b/hccapx/java.html
@@ -501,7 +501,7 @@ <h3>Hccapx.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/javascript.html b/hccapx/javascript.html
index b78ce8979..3fab680f6 100644
--- a/hccapx/javascript.html
+++ b/hccapx/javascript.html
@@ -439,7 +439,7 @@ <h3>Hccapx.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/lua.html b/hccapx/lua.html
index 4ec1a6619..391dbf2b4 100644
--- a/hccapx/lua.html
+++ b/hccapx/lua.html
@@ -370,7 +370,7 @@ <h3>hccapx.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/nim.html b/hccapx/nim.html
index 281cdeffb..3504bbe85 100644
--- a/hccapx/nim.html
+++ b/hccapx/nim.html
@@ -431,7 +431,7 @@ <h3>hccapx.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/perl.html b/hccapx/perl.html
index f3d9ea573..b51a1c3c7 100644
--- a/hccapx/perl.html
+++ b/hccapx/perl.html
@@ -437,7 +437,7 @@ <h3>Hccapx.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/php.html b/hccapx/php.html
index b8e022b10..46fc70389 100644
--- a/hccapx/php.html
+++ b/hccapx/php.html
@@ -419,7 +419,7 @@ <h3>Hccapx.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/python.html b/hccapx/python.html
index e23d00258..c8b7439cb 100644
--- a/hccapx/python.html
+++ b/hccapx/python.html
@@ -360,7 +360,7 @@ <h3>hccapx.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/hccapx/ruby.html b/hccapx/ruby.html
index 9250b2b4c..3db294535 100644
--- a/hccapx/ruby.html
+++ b/hccapx/ruby.html
@@ -434,7 +434,7 @@ <h3>hccapx.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/cpp_stl_11.html b/heaps_pak/cpp_stl_11.html
index 3520c839c..3ebd65e32 100644
--- a/heaps_pak/cpp_stl_11.html
+++ b/heaps_pak/cpp_stl_11.html
@@ -727,7 +727,7 @@ <h3>heaps_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/cpp_stl_98.html b/heaps_pak/cpp_stl_98.html
index c91bb30ca..b7765a84e 100644
--- a/heaps_pak/cpp_stl_98.html
+++ b/heaps_pak/cpp_stl_98.html
@@ -786,7 +786,7 @@ <h3>heaps_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/csharp.html b/heaps_pak/csharp.html
index 22acd43da..1971c117e 100644
--- a/heaps_pak/csharp.html
+++ b/heaps_pak/csharp.html
@@ -540,7 +540,7 @@ <h3>HeapsPak.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/go.html b/heaps_pak/go.html
index b76983856..92cd2989e 100644
--- a/heaps_pak/go.html
+++ b/heaps_pak/go.html
@@ -550,7 +550,7 @@ <h3>heaps_pak.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/graphviz.html b/heaps_pak/graphviz.html
index 44a29cad4..3d105e1f1 100644
--- a/heaps_pak/graphviz.html
+++ b/heaps_pak/graphviz.html
@@ -353,7 +353,7 @@ <h3>heaps_pak.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/index.html b/heaps_pak/index.html
index e20bf7688..5b7e60545 100644
--- a/heaps_pak/index.html
+++ b/heaps_pak/index.html
@@ -319,7 +319,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/java.html b/heaps_pak/java.html
index 0ea59f374..c0b907398 100644
--- a/heaps_pak/java.html
+++ b/heaps_pak/java.html
@@ -563,7 +563,7 @@ <h3>HeapsPak.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/javascript.html b/heaps_pak/javascript.html
index 8bb7f2cd2..1c0713309 100644
--- a/heaps_pak/javascript.html
+++ b/heaps_pak/javascript.html
@@ -450,7 +450,7 @@ <h3>HeapsPak.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/lua.html b/heaps_pak/lua.html
index 26b4acf87..de988c08c 100644
--- a/heaps_pak/lua.html
+++ b/heaps_pak/lua.html
@@ -396,7 +396,7 @@ <h3>heaps_pak.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/nim.html b/heaps_pak/nim.html
index 353c405af..f1e552932 100644
--- a/heaps_pak/nim.html
+++ b/heaps_pak/nim.html
@@ -443,7 +443,7 @@ <h3>heaps_pak.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/perl.html b/heaps_pak/perl.html
index 359359b5d..f6ff2cbb6 100644
--- a/heaps_pak/perl.html
+++ b/heaps_pak/perl.html
@@ -595,7 +595,7 @@ <h3>HeapsPak.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/php.html b/heaps_pak/php.html
index e7eac6c2f..cec3d9e9f 100644
--- a/heaps_pak/php.html
+++ b/heaps_pak/php.html
@@ -419,7 +419,7 @@ <h3>HeapsPak.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/python.html b/heaps_pak/python.html
index b386f868c..14f383ef2 100644
--- a/heaps_pak/python.html
+++ b/heaps_pak/python.html
@@ -418,7 +418,7 @@ <h3>heaps_pak.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heaps_pak/ruby.html b/heaps_pak/ruby.html
index 714fb786d..13b4db833 100644
--- a/heaps_pak/ruby.html
+++ b/heaps_pak/ruby.html
@@ -433,7 +433,7 @@ <h3>heaps_pak.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/cpp_stl_11.html b/heroes_of_might_and_magic_agg/cpp_stl_11.html
index 08ab26241..cb9b3fd96 100644
--- a/heroes_of_might_and_magic_agg/cpp_stl_11.html
+++ b/heroes_of_might_and_magic_agg/cpp_stl_11.html
@@ -573,7 +573,7 @@ <h3>heroes_of_might_and_magic_agg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/cpp_stl_98.html b/heroes_of_might_and_magic_agg/cpp_stl_98.html
index e3fe8397f..f2b7776be 100644
--- a/heroes_of_might_and_magic_agg/cpp_stl_98.html
+++ b/heroes_of_might_and_magic_agg/cpp_stl_98.html
@@ -614,7 +614,7 @@ <h3>heroes_of_might_and_magic_agg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/csharp.html b/heroes_of_might_and_magic_agg/csharp.html
index 0baf25cde..fc3cfa472 100644
--- a/heroes_of_might_and_magic_agg/csharp.html
+++ b/heroes_of_might_and_magic_agg/csharp.html
@@ -443,7 +443,7 @@ <h3>HeroesOfMightAndMagicAgg.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/go.html b/heroes_of_might_and_magic_agg/go.html
index 40723bdd7..a55d45fab 100644
--- a/heroes_of_might_and_magic_agg/go.html
+++ b/heroes_of_might_and_magic_agg/go.html
@@ -437,7 +437,7 @@ <h3>heroes_of_might_and_magic_agg.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/graphviz.html b/heroes_of_might_and_magic_agg/graphviz.html
index 03f2f4d84..99d8ded9d 100644
--- a/heroes_of_might_and_magic_agg/graphviz.html
+++ b/heroes_of_might_and_magic_agg/graphviz.html
@@ -312,7 +312,7 @@ <h3>heroes_of_might_and_magic_agg.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/index.html b/heroes_of_might_and_magic_agg/index.html
index 5e68502aa..2d5d6d5b2 100644
--- a/heroes_of_might_and_magic_agg/index.html
+++ b/heroes_of_might_and_magic_agg/index.html
@@ -287,7 +287,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/java.html b/heroes_of_might_and_magic_agg/java.html
index 9b012fed5..1d1ba314a 100644
--- a/heroes_of_might_and_magic_agg/java.html
+++ b/heroes_of_might_and_magic_agg/java.html
@@ -446,7 +446,7 @@ <h3>HeroesOfMightAndMagicAgg.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/javascript.html b/heroes_of_might_and_magic_agg/javascript.html
index 30963c035..299318f4d 100644
--- a/heroes_of_might_and_magic_agg/javascript.html
+++ b/heroes_of_might_and_magic_agg/javascript.html
@@ -394,7 +394,7 @@ <h3>HeroesOfMightAndMagicAgg.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/lua.html b/heroes_of_might_and_magic_agg/lua.html
index e2d047b1b..d0cd546d4 100644
--- a/heroes_of_might_and_magic_agg/lua.html
+++ b/heroes_of_might_and_magic_agg/lua.html
@@ -349,7 +349,7 @@ <h3>heroes_of_might_and_magic_agg.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/nim.html b/heroes_of_might_and_magic_agg/nim.html
index a8ce429e3..bd1403058 100644
--- a/heroes_of_might_and_magic_agg/nim.html
+++ b/heroes_of_might_and_magic_agg/nim.html
@@ -369,7 +369,7 @@ <h3>heroes_of_might_and_magic_agg.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/perl.html b/heroes_of_might_and_magic_agg/perl.html
index 077aec208..7e9a5bf35 100644
--- a/heroes_of_might_and_magic_agg/perl.html
+++ b/heroes_of_might_and_magic_agg/perl.html
@@ -441,7 +441,7 @@ <h3>HeroesOfMightAndMagicAgg.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/php.html b/heroes_of_might_and_magic_agg/php.html
index fd766b320..d0ab3d901 100644
--- a/heroes_of_might_and_magic_agg/php.html
+++ b/heroes_of_might_and_magic_agg/php.html
@@ -351,7 +351,7 @@ <h3>HeroesOfMightAndMagicAgg.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/python.html b/heroes_of_might_and_magic_agg/python.html
index 668ebaecc..03f8a4bf4 100644
--- a/heroes_of_might_and_magic_agg/python.html
+++ b/heroes_of_might_and_magic_agg/python.html
@@ -382,7 +382,7 @@ <h3>heroes_of_might_and_magic_agg.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_agg/ruby.html b/heroes_of_might_and_magic_agg/ruby.html
index 47baf1360..7e3b3dffe 100644
--- a/heroes_of_might_and_magic_agg/ruby.html
+++ b/heroes_of_might_and_magic_agg/ruby.html
@@ -382,7 +382,7 @@ <h3>heroes_of_might_and_magic_agg.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/cpp_stl_11.html b/heroes_of_might_and_magic_bmp/cpp_stl_11.html
index ab64041f0..44a8cea13 100644
--- a/heroes_of_might_and_magic_bmp/cpp_stl_11.html
+++ b/heroes_of_might_and_magic_bmp/cpp_stl_11.html
@@ -418,7 +418,7 @@ <h3>heroes_of_might_and_magic_bmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/cpp_stl_98.html b/heroes_of_might_and_magic_bmp/cpp_stl_98.html
index e4d4a8a2c..3b964bb2a 100644
--- a/heroes_of_might_and_magic_bmp/cpp_stl_98.html
+++ b/heroes_of_might_and_magic_bmp/cpp_stl_98.html
@@ -426,7 +426,7 @@ <h3>heroes_of_might_and_magic_bmp.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/csharp.html b/heroes_of_might_and_magic_bmp/csharp.html
index cc5063a7f..c3c907939 100644
--- a/heroes_of_might_and_magic_bmp/csharp.html
+++ b/heroes_of_might_and_magic_bmp/csharp.html
@@ -341,7 +341,7 @@ <h3>HeroesOfMightAndMagicBmp.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/go.html b/heroes_of_might_and_magic_bmp/go.html
index 5ab2d53dc..3800beca1 100644
--- a/heroes_of_might_and_magic_bmp/go.html
+++ b/heroes_of_might_and_magic_bmp/go.html
@@ -305,7 +305,7 @@ <h3>heroes_of_might_and_magic_bmp.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/graphviz.html b/heroes_of_might_and_magic_bmp/graphviz.html
index 1b1ce5ad0..ad4b3ab86 100644
--- a/heroes_of_might_and_magic_bmp/graphviz.html
+++ b/heroes_of_might_and_magic_bmp/graphviz.html
@@ -277,7 +277,7 @@ <h3>heroes_of_might_and_magic_bmp.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/index.html b/heroes_of_might_and_magic_bmp/index.html
index cabecd146..2836dee54 100644
--- a/heroes_of_might_and_magic_bmp/index.html
+++ b/heroes_of_might_and_magic_bmp/index.html
@@ -261,7 +261,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/java.html b/heroes_of_might_and_magic_bmp/java.html
index 6ea90167e..d5b22fd12 100644
--- a/heroes_of_might_and_magic_bmp/java.html
+++ b/heroes_of_might_and_magic_bmp/java.html
@@ -348,7 +348,7 @@ <h3>HeroesOfMightAndMagicBmp.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/javascript.html b/heroes_of_might_and_magic_bmp/javascript.html
index 6ea0f5ee9..141470dea 100644
--- a/heroes_of_might_and_magic_bmp/javascript.html
+++ b/heroes_of_might_and_magic_bmp/javascript.html
@@ -328,7 +328,7 @@ <h3>HeroesOfMightAndMagicBmp.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/lua.html b/heroes_of_might_and_magic_bmp/lua.html
index 7cc79f3c1..f23c63a8e 100644
--- a/heroes_of_might_and_magic_bmp/lua.html
+++ b/heroes_of_might_and_magic_bmp/lua.html
@@ -281,7 +281,7 @@ <h3>heroes_of_might_and_magic_bmp.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/nim.html b/heroes_of_might_and_magic_bmp/nim.html
index 0be90da30..57f287d8f 100644
--- a/heroes_of_might_and_magic_bmp/nim.html
+++ b/heroes_of_might_and_magic_bmp/nim.html
@@ -292,7 +292,7 @@ <h3>heroes_of_might_and_magic_bmp.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/perl.html b/heroes_of_might_and_magic_bmp/perl.html
index 6a0792847..642cd8b48 100644
--- a/heroes_of_might_and_magic_bmp/perl.html
+++ b/heroes_of_might_and_magic_bmp/perl.html
@@ -322,7 +322,7 @@ <h3>HeroesOfMightAndMagicBmp.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/php.html b/heroes_of_might_and_magic_bmp/php.html
index 424d084ea..c38b3ccc9 100644
--- a/heroes_of_might_and_magic_bmp/php.html
+++ b/heroes_of_might_and_magic_bmp/php.html
@@ -285,7 +285,7 @@ <h3>HeroesOfMightAndMagicBmp.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/python.html b/heroes_of_might_and_magic_bmp/python.html
index 08ab4f05b..5e11d4ed5 100644
--- a/heroes_of_might_and_magic_bmp/python.html
+++ b/heroes_of_might_and_magic_bmp/python.html
@@ -324,7 +324,7 @@ <h3>heroes_of_might_and_magic_bmp.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/heroes_of_might_and_magic_bmp/ruby.html b/heroes_of_might_and_magic_bmp/ruby.html
index b63d9c5ff..0c6216525 100644
--- a/heroes_of_might_and_magic_bmp/ruby.html
+++ b/heroes_of_might_and_magic_bmp/ruby.html
@@ -327,7 +327,7 @@ <h3>heroes_of_might_and_magic_bmp.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icc_4/graphviz.html b/icc_4/graphviz.html
index e8fccaee7..5e55b3a09 100644
--- a/icc_4/graphviz.html
+++ b/icc_4/graphviz.html
@@ -2000,7 +2000,7 @@ <h3>icc_4.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icc_4/index.html b/icc_4/index.html
index 8137bf746..a07e2c342 100644
--- a/icc_4/index.html
+++ b/icc_4/index.html
@@ -1927,7 +1927,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icc_4/nim.html b/icc_4/nim.html
index 3c971a066..987b4b978 100644
--- a/icc_4/nim.html
+++ b/icc_4/nim.html
@@ -3851,7 +3851,7 @@ <h3>icc_4.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icc_4/perl.html b/icc_4/perl.html
index 52ca3b30d..6d06fb473 100644
--- a/icc_4/perl.html
+++ b/icc_4/perl.html
@@ -6595,7 +6595,7 @@ <h3>Icc4.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/cpp_stl_11.html b/icmp_packet/cpp_stl_11.html
index 56345ed5c..b5a0ae543 100644
--- a/icmp_packet/cpp_stl_11.html
+++ b/icmp_packet/cpp_stl_11.html
@@ -648,7 +648,7 @@ <h3>icmp_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/cpp_stl_98.html b/icmp_packet/cpp_stl_98.html
index f0403338a..a80f6188c 100644
--- a/icmp_packet/cpp_stl_98.html
+++ b/icmp_packet/cpp_stl_98.html
@@ -683,7 +683,7 @@ <h3>icmp_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/csharp.html b/icmp_packet/csharp.html
index 363584f0f..c6c071f2e 100644
--- a/icmp_packet/csharp.html
+++ b/icmp_packet/csharp.html
@@ -487,7 +487,7 @@ <h3>IcmpPacket.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/go.html b/icmp_packet/go.html
index 049553f26..18b72ab30 100644
--- a/icmp_packet/go.html
+++ b/icmp_packet/go.html
@@ -472,7 +472,7 @@ <h3>icmp_packet.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/graphviz.html b/icmp_packet/graphviz.html
index c4cf936ac..238b1943a 100644
--- a/icmp_packet/graphviz.html
+++ b/icmp_packet/graphviz.html
@@ -321,7 +321,7 @@ <h3>icmp_packet.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/index.html b/icmp_packet/index.html
index 4dfc9103e..f40e3c542 100644
--- a/icmp_packet/index.html
+++ b/icmp_packet/index.html
@@ -334,7 +334,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/java.html b/icmp_packet/java.html
index 06dd0bd43..3c53b951e 100644
--- a/icmp_packet/java.html
+++ b/icmp_packet/java.html
@@ -538,7 +538,7 @@ <h3>IcmpPacket.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/javascript.html b/icmp_packet/javascript.html
index 3c77e1688..59a46e88d 100644
--- a/icmp_packet/javascript.html
+++ b/icmp_packet/javascript.html
@@ -458,7 +458,7 @@ <h3>IcmpPacket.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/lua.html b/icmp_packet/lua.html
index 88e29e4e8..640e3edec 100644
--- a/icmp_packet/lua.html
+++ b/icmp_packet/lua.html
@@ -382,7 +382,7 @@ <h3>icmp_packet.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/nim.html b/icmp_packet/nim.html
index cdb554b5a..353f1797e 100644
--- a/icmp_packet/nim.html
+++ b/icmp_packet/nim.html
@@ -404,7 +404,7 @@ <h3>icmp_packet.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/perl.html b/icmp_packet/perl.html
index d1b0eb5a7..fa55fb771 100644
--- a/icmp_packet/perl.html
+++ b/icmp_packet/perl.html
@@ -515,7 +515,7 @@ <h3>IcmpPacket.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/php.html b/icmp_packet/php.html
index b3978ec1d..cac5ba8f2 100644
--- a/icmp_packet/php.html
+++ b/icmp_packet/php.html
@@ -406,7 +406,7 @@ <h3>IcmpPacket.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/python.html b/icmp_packet/python.html
index dfbb374d8..91f733b7b 100644
--- a/icmp_packet/python.html
+++ b/icmp_packet/python.html
@@ -411,7 +411,7 @@ <h3>icmp_packet.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/icmp_packet/ruby.html b/icmp_packet/ruby.html
index f927bf955..fec44b5eb 100644
--- a/icmp_packet/ruby.html
+++ b/icmp_packet/ruby.html
@@ -428,7 +428,7 @@ <h3>icmp_packet.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/cpp_stl_11.html b/ico/cpp_stl_11.html
index 2d501a02f..82913c34d 100644
--- a/ico/cpp_stl_11.html
+++ b/ico/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -626,7 +626,7 @@ <h3>ico.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/cpp_stl_98.html b/ico/cpp_stl_98.html
index 0b7a185fb..53e09d404 100644
--- a/ico/cpp_stl_98.html
+++ b/ico/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -646,7 +646,7 @@ <h3>ico.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/csharp.html b/ico/csharp.html
index 3c7f12a34..58e28f42d 100644
--- a/ico/csharp.html
+++ b/ico/csharp.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -522,7 +522,7 @@ <h3>Ico.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/go.html b/ico/go.html
index 9ede6950d..c79e0f506 100644
--- a/ico/go.html
+++ b/ico/go.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -526,7 +526,7 @@ <h3>ico.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/graphviz.html b/ico/graphviz.html
index 29f3d68e1..f00ff160d 100644
--- a/ico/graphviz.html
+++ b/ico/graphviz.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -330,7 +330,7 @@ <h3>ico.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/index.html b/ico/index.html
index 4cc9749c5..8858f7628 100644
--- a/ico/index.html
+++ b/ico/index.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -354,7 +354,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/java.html b/ico/java.html
index 01000a1b3..1157fd439 100644
--- a/ico/java.html
+++ b/ico/java.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -511,7 +511,7 @@ <h3>Ico.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/javascript.html b/ico/javascript.html
index 7a0ed6b0c..44c048d1d 100644
--- a/ico/javascript.html
+++ b/ico/javascript.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -465,7 +465,7 @@ <h3>Ico.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/lua.html b/ico/lua.html
index dd660d5cf..0e9fd6a98 100644
--- a/ico/lua.html
+++ b/ico/lua.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -400,7 +400,7 @@ <h3>ico.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/nim.html b/ico/nim.html
index 4fa461efb..e4c4a700a 100644
--- a/ico/nim.html
+++ b/ico/nim.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -449,7 +449,7 @@ <h3>ico.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/perl.html b/ico/perl.html
index 9d9b98fec..26f64a1c0 100644
--- a/ico/perl.html
+++ b/ico/perl.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h3>Ico.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/php.html b/ico/php.html
index 9a193b696..bba1c82c0 100644
--- a/ico/php.html
+++ b/ico/php.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -431,7 +431,7 @@ <h3>Ico.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/python.html b/ico/python.html
index 347a60326..12d0e33e3 100644
--- a/ico/python.html
+++ b/ico/python.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -414,7 +414,7 @@ <h3>ico.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ico/ruby.html b/ico/ruby.html
index 742a95489..670fc1f13 100644
--- a/ico/ruby.html
+++ b/ico/ruby.html
@@ -105,9 +105,9 @@ <h1>Microsoft Windows icon file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows uses specific file format to store applications
-icons - ICO. This is a container that contains one or more image
-files (effectively, DIB parts of BMP files or full PNG files are
+                <p><p>Microsoft Windows uses specific file format to store applications<br />
+icons - ICO. This is a container that contains one or more image<br />
+files (effectively, DIB parts of BMP files or full PNG files are<br />
 contained inside).</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>ico.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/cpp_stl_11.html b/id3v1_1/cpp_stl_11.html
index 1d0cdb494..0f95471a2 100644
--- a/id3v1_1/cpp_stl_11.html
+++ b/id3v1_1/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -685,7 +685,7 @@ <h3>id3v1_1.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/cpp_stl_98.html b/id3v1_1/cpp_stl_98.html
index 237c2b327..aa3a9c9c4 100644
--- a/id3v1_1/cpp_stl_98.html
+++ b/id3v1_1/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -702,7 +702,7 @@ <h3>id3v1_1.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/csharp.html b/id3v1_1/csharp.html
index 43dacc757..2a622adcd 100644
--- a/id3v1_1/csharp.html
+++ b/id3v1_1/csharp.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h3>Id3v11.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/go.html b/id3v1_1/go.html
index f792954bd..0d147ae98 100644
--- a/id3v1_1/go.html
+++ b/id3v1_1/go.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -578,7 +578,7 @@ <h3>id3v1_1.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/graphviz.html b/id3v1_1/graphviz.html
index f41ec79d0..8c751902f 100644
--- a/id3v1_1/graphviz.html
+++ b/id3v1_1/graphviz.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -313,7 +313,7 @@ <h3>id3v1_1.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/index.html b/id3v1_1/index.html
index ce0e0117c..0f72b1017 100644
--- a/id3v1_1/index.html
+++ b/id3v1_1/index.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -453,7 +453,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/java.html b/id3v1_1/java.html
index 4033f9a14..ee089fe37 100644
--- a/id3v1_1/java.html
+++ b/id3v1_1/java.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -603,7 +603,7 @@ <h3>Id3v11.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/javascript.html b/id3v1_1/javascript.html
index f0cac0359..e771d28d2 100644
--- a/id3v1_1/javascript.html
+++ b/id3v1_1/javascript.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -679,7 +679,7 @@ <h3>Id3v11.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/lua.html b/id3v1_1/lua.html
index 9000c50f6..2941b1224 100644
--- a/id3v1_1/lua.html
+++ b/id3v1_1/lua.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -495,7 +495,7 @@ <h3>id3v1_1.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/nim.html b/id3v1_1/nim.html
index fe1ed91c4..97b9f3b0e 100644
--- a/id3v1_1/nim.html
+++ b/id3v1_1/nim.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -523,7 +523,7 @@ <h3>id3v1_1.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/perl.html b/id3v1_1/perl.html
index b522a93b0..69d248470 100644
--- a/id3v1_1/perl.html
+++ b/id3v1_1/perl.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -532,7 +532,7 @@ <h3>Id3v11.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/php.html b/id3v1_1/php.html
index 9c4682656..be0de63ef 100644
--- a/id3v1_1/php.html
+++ b/id3v1_1/php.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -513,7 +513,7 @@ <h3>Id3v11.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/python.html b/id3v1_1/python.html
index fb349103b..a4a775fa4 100644
--- a/id3v1_1/python.html
+++ b/id3v1_1/python.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -522,7 +522,7 @@ <h3>id3v1_1.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v1_1/ruby.html b/id3v1_1/ruby.html
index cfc46ade8..d7f7beebf 100644
--- a/id3v1_1/ruby.html
+++ b/id3v1_1/ruby.html
@@ -105,10 +105,10 @@ <h1>ID3v1.1 tag for .mp3 files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The
+                <p><p>ID3v1.1 tag is a method to store simple metadata in .mp3 files. The<br />
 tag is appended to the end of file and spans exactly 128 bytes.</p>
-<p>This type is supposed to be used on full .mp3 files, seeking to
-proper position automatically. If you're interesting in parsing only
+<p>This type is supposed to be used on full .mp3 files, seeking to<br />
+proper position automatically. If you're interesting in parsing only<br />
 the tag itself, please use <code>id3v1_1::id3_v1_1_tag</code> subtype.</p>
 </p>
             </div>
@@ -539,7 +539,7 @@ <h3>id3v1_1.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/cpp_stl_11.html b/id3v2_3/cpp_stl_11.html
index a9d946298..e21cba166 100644
--- a/id3v2_3/cpp_stl_11.html
+++ b/id3v2_3/cpp_stl_11.html
@@ -1059,7 +1059,7 @@ <h3>id3v2_3.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/cpp_stl_98.html b/id3v2_3/cpp_stl_98.html
index bcf934202..c423342bc 100644
--- a/id3v2_3/cpp_stl_98.html
+++ b/id3v2_3/cpp_stl_98.html
@@ -1166,7 +1166,7 @@ <h3>id3v2_3.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/csharp.html b/id3v2_3/csharp.html
index 018ed8776..947ab09b6 100644
--- a/id3v2_3/csharp.html
+++ b/id3v2_3/csharp.html
@@ -757,7 +757,7 @@ <h3>Id3v23.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/go.html b/id3v2_3/go.html
index 99d38a5c8..fd2dd70a5 100644
--- a/id3v2_3/go.html
+++ b/id3v2_3/go.html
@@ -805,7 +805,7 @@ <h3>id3v2_3.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/graphviz.html b/id3v2_3/graphviz.html
index 301eaaaf2..7aa58e15c 100644
--- a/id3v2_3/graphviz.html
+++ b/id3v2_3/graphviz.html
@@ -441,7 +441,7 @@ <h3>id3v2_3.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/index.html b/id3v2_3/index.html
index a3f157ca8..8405fb4fc 100644
--- a/id3v2_3/index.html
+++ b/id3v2_3/index.html
@@ -406,7 +406,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/java.html b/id3v2_3/java.html
index 73d3fbdca..8b5ab27f8 100644
--- a/id3v2_3/java.html
+++ b/id3v2_3/java.html
@@ -794,7 +794,7 @@ <h3>Id3v23.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/javascript.html b/id3v2_3/javascript.html
index f9e5243ea..c25aa2632 100644
--- a/id3v2_3/javascript.html
+++ b/id3v2_3/javascript.html
@@ -580,7 +580,7 @@ <h3>Id3v23.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/lua.html b/id3v2_3/lua.html
index 7a065f934..2100f29c5 100644
--- a/id3v2_3/lua.html
+++ b/id3v2_3/lua.html
@@ -523,7 +523,7 @@ <h3>id3v2_3.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/nim.html b/id3v2_3/nim.html
index 1d5bd6ddb..53cb5e976 100644
--- a/id3v2_3/nim.html
+++ b/id3v2_3/nim.html
@@ -625,7 +625,7 @@ <h3>id3v2_3.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/perl.html b/id3v2_3/perl.html
index a65656d7d..067d124ba 100644
--- a/id3v2_3/perl.html
+++ b/id3v2_3/perl.html
@@ -895,7 +895,7 @@ <h3>Id3v23.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/php.html b/id3v2_3/php.html
index 113c7796f..6b4eddda2 100644
--- a/id3v2_3/php.html
+++ b/id3v2_3/php.html
@@ -568,7 +568,7 @@ <h3>Id3v23.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/python.html b/id3v2_3/python.html
index 81d17eaad..77fa9e32f 100644
--- a/id3v2_3/python.html
+++ b/id3v2_3/python.html
@@ -534,7 +534,7 @@ <h3>id3v2_3.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_3/ruby.html b/id3v2_3/ruby.html
index f9283873b..afaf26875 100644
--- a/id3v2_3/ruby.html
+++ b/id3v2_3/ruby.html
@@ -557,7 +557,7 @@ <h3>id3v2_3.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/cpp_stl_11.html b/id3v2_4/cpp_stl_11.html
index 945c4360c..013d71c4d 100644
--- a/id3v2_4/cpp_stl_11.html
+++ b/id3v2_4/cpp_stl_11.html
@@ -1268,7 +1268,7 @@ <h3>id3v2_4.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/cpp_stl_98.html b/id3v2_4/cpp_stl_98.html
index 36916b799..bf0e2f2dd 100644
--- a/id3v2_4/cpp_stl_98.html
+++ b/id3v2_4/cpp_stl_98.html
@@ -1420,7 +1420,7 @@ <h3>id3v2_4.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/csharp.html b/id3v2_4/csharp.html
index 221f5a178..586f98ac8 100644
--- a/id3v2_4/csharp.html
+++ b/id3v2_4/csharp.html
@@ -886,7 +886,7 @@ <h3>Id3v24.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/go.html b/id3v2_4/go.html
index 70fde52bb..f4817c851 100644
--- a/id3v2_4/go.html
+++ b/id3v2_4/go.html
@@ -1004,7 +1004,7 @@ <h3>id3v2_4.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/graphviz.html b/id3v2_4/graphviz.html
index 96931973c..9a60fa24e 100644
--- a/id3v2_4/graphviz.html
+++ b/id3v2_4/graphviz.html
@@ -501,7 +501,7 @@ <h3>id3v2_4.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/index.html b/id3v2_4/index.html
index f5ea26d90..6b4ffe1bf 100644
--- a/id3v2_4/index.html
+++ b/id3v2_4/index.html
@@ -459,7 +459,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/java.html b/id3v2_4/java.html
index 706c94798..11af3aadb 100644
--- a/id3v2_4/java.html
+++ b/id3v2_4/java.html
@@ -944,7 +944,7 @@ <h3>Id3v24.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/javascript.html b/id3v2_4/javascript.html
index 0db4b96bf..5bd1fb872 100644
--- a/id3v2_4/javascript.html
+++ b/id3v2_4/javascript.html
@@ -642,7 +642,7 @@ <h3>Id3v24.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/lua.html b/id3v2_4/lua.html
index dfc36299c..3da09fb37 100644
--- a/id3v2_4/lua.html
+++ b/id3v2_4/lua.html
@@ -589,7 +589,7 @@ <h3>id3v2_4.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/nim.html b/id3v2_4/nim.html
index f881e83af..3e83a323e 100644
--- a/id3v2_4/nim.html
+++ b/id3v2_4/nim.html
@@ -728,7 +728,7 @@ <h3>id3v2_4.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/perl.html b/id3v2_4/perl.html
index 5a38d6870..a2f76a0fb 100644
--- a/id3v2_4/perl.html
+++ b/id3v2_4/perl.html
@@ -1143,7 +1143,7 @@ <h3>Id3v24.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/php.html b/id3v2_4/php.html
index 94f6aecea..bee4154a2 100644
--- a/id3v2_4/php.html
+++ b/id3v2_4/php.html
@@ -671,7 +671,7 @@ <h3>Id3v24.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/python.html b/id3v2_4/python.html
index 587c6e003..dcfe8296c 100644
--- a/id3v2_4/python.html
+++ b/id3v2_4/python.html
@@ -582,7 +582,7 @@ <h3>id3v2_4.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/id3v2_4/ruby.html b/id3v2_4/ruby.html
index fdc0b88d9..6d11a19dc 100644
--- a/id3v2_4/ruby.html
+++ b/id3v2_4/ruby.html
@@ -625,7 +625,7 @@ <h3>id3v2_4.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/index.html b/index.html
index f497695d7..d6c84074a 100644
--- a/index.html
+++ b/index.html
@@ -1166,7 +1166,7 @@ <h1>Contributing</h1>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/cpp_stl_11.html b/ines/cpp_stl_11.html
index 84caea599..bfb4a8832 100644
--- a/ines/cpp_stl_11.html
+++ b/ines/cpp_stl_11.html
@@ -991,7 +991,7 @@ <h3>ines.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/cpp_stl_98.html b/ines/cpp_stl_98.html
index 967f4af53..88cb93745 100644
--- a/ines/cpp_stl_98.html
+++ b/ines/cpp_stl_98.html
@@ -1077,7 +1077,7 @@ <h3>ines.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/csharp.html b/ines/csharp.html
index d3e9584d1..e941a8328 100644
--- a/ines/csharp.html
+++ b/ines/csharp.html
@@ -738,7 +738,7 @@ <h3>Ines.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/go.html b/ines/go.html
index ee3c637c0..96e742281 100644
--- a/ines/go.html
+++ b/ines/go.html
@@ -803,7 +803,7 @@ <h3>ines.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/graphviz.html b/ines/graphviz.html
index 38f4a60cc..57319bccd 100644
--- a/ines/graphviz.html
+++ b/ines/graphviz.html
@@ -370,7 +370,7 @@ <h3>ines.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/index.html b/ines/index.html
index 8f227366c..91ce09c53 100644
--- a/ines/index.html
+++ b/ines/index.html
@@ -391,7 +391,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/java.html b/ines/java.html
index 957207030..572f4662d 100644
--- a/ines/java.html
+++ b/ines/java.html
@@ -803,7 +803,7 @@ <h3>Ines.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/javascript.html b/ines/javascript.html
index 10a5d8bf1..9107aff54 100644
--- a/ines/javascript.html
+++ b/ines/javascript.html
@@ -604,7 +604,7 @@ <h3>Ines.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/lua.html b/ines/lua.html
index e82cd17b4..ad82ee396 100644
--- a/ines/lua.html
+++ b/ines/lua.html
@@ -496,7 +496,7 @@ <h3>ines.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/nim.html b/ines/nim.html
index 1df44d3c0..6f0f78027 100644
--- a/ines/nim.html
+++ b/ines/nim.html
@@ -624,7 +624,7 @@ <h3>ines.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/perl.html b/ines/perl.html
index 649c6c748..dfcd3ad2c 100644
--- a/ines/perl.html
+++ b/ines/perl.html
@@ -785,7 +785,7 @@ <h3>Ines.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/php.html b/ines/php.html
index b23185fcc..6c59d0df1 100644
--- a/ines/php.html
+++ b/ines/php.html
@@ -585,7 +585,7 @@ <h3>Ines.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/python.html b/ines/python.html
index 2101d04a1..e23496881 100644
--- a/ines/python.html
+++ b/ines/python.html
@@ -487,7 +487,7 @@ <h3>ines.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ines/ruby.html b/ines/ruby.html
index 557d50e37..6a26228ad 100644
--- a/ines/ruby.html
+++ b/ines/ruby.html
@@ -572,7 +572,7 @@ <h3>ines.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/cpp_stl_11.html b/ipv4_packet/cpp_stl_11.html
index 0135b73b3..74d938628 100644
--- a/ipv4_packet/cpp_stl_11.html
+++ b/ipv4_packet/cpp_stl_11.html
@@ -669,7 +669,7 @@ <h3>ipv4_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/cpp_stl_98.html b/ipv4_packet/cpp_stl_98.html
index 2a8ad9f93..3d27fca69 100644
--- a/ipv4_packet/cpp_stl_98.html
+++ b/ipv4_packet/cpp_stl_98.html
@@ -707,7 +707,7 @@ <h3>ipv4_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/csharp.html b/ipv4_packet/csharp.html
index f2bd12d59..c370e5bf4 100644
--- a/ipv4_packet/csharp.html
+++ b/ipv4_packet/csharp.html
@@ -532,7 +532,7 @@ <h3>Ipv4Packet.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/go.html b/ipv4_packet/go.html
index 14e7de168..f950d232f 100644
--- a/ipv4_packet/go.html
+++ b/ipv4_packet/go.html
@@ -536,7 +536,7 @@ <h3>ipv4_packet.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/graphviz.html b/ipv4_packet/graphviz.html
index d588bcb78..58e38a6a2 100644
--- a/ipv4_packet/graphviz.html
+++ b/ipv4_packet/graphviz.html
@@ -356,7 +356,7 @@ <h3>ipv4_packet.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/index.html b/ipv4_packet/index.html
index 40a477c1b..0b8f1f7a5 100644
--- a/ipv4_packet/index.html
+++ b/ipv4_packet/index.html
@@ -325,7 +325,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/java.html b/ipv4_packet/java.html
index ad6bb843f..3f4e5a113 100644
--- a/ipv4_packet/java.html
+++ b/ipv4_packet/java.html
@@ -514,7 +514,7 @@ <h3>Ipv4Packet.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/javascript.html b/ipv4_packet/javascript.html
index aba38b80c..ec695b6be 100644
--- a/ipv4_packet/javascript.html
+++ b/ipv4_packet/javascript.html
@@ -439,7 +439,7 @@ <h3>Ipv4Packet.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/lua.html b/ipv4_packet/lua.html
index 75d5c8c39..5c4e6d47f 100644
--- a/ipv4_packet/lua.html
+++ b/ipv4_packet/lua.html
@@ -405,7 +405,7 @@ <h3>ipv4_packet.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/nim.html b/ipv4_packet/nim.html
index aa5e78b86..15301d5d3 100644
--- a/ipv4_packet/nim.html
+++ b/ipv4_packet/nim.html
@@ -452,7 +452,7 @@ <h3>ipv4_packet.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/perl.html b/ipv4_packet/perl.html
index 700cc1370..0419f4abf 100644
--- a/ipv4_packet/perl.html
+++ b/ipv4_packet/perl.html
@@ -532,7 +532,7 @@ <h3>Ipv4Packet.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/php.html b/ipv4_packet/php.html
index 0ca598308..98b28075e 100644
--- a/ipv4_packet/php.html
+++ b/ipv4_packet/php.html
@@ -414,7 +414,7 @@ <h3>Ipv4Packet.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/python.html b/ipv4_packet/python.html
index e9b5fe19c..50f9dfff4 100644
--- a/ipv4_packet/python.html
+++ b/ipv4_packet/python.html
@@ -428,7 +428,7 @@ <h3>ipv4_packet.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv4_packet/ruby.html b/ipv4_packet/ruby.html
index 96ef9d4aa..917fd904e 100644
--- a/ipv4_packet/ruby.html
+++ b/ipv4_packet/ruby.html
@@ -426,7 +426,7 @@ <h3>ipv4_packet.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/cpp_stl_11.html b/ipv6_packet/cpp_stl_11.html
index decc37b5d..a07ce6eb9 100644
--- a/ipv6_packet/cpp_stl_11.html
+++ b/ipv6_packet/cpp_stl_11.html
@@ -430,7 +430,7 @@ <h3>ipv6_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/cpp_stl_98.html b/ipv6_packet/cpp_stl_98.html
index 1cd221f60..6ca3b589a 100644
--- a/ipv6_packet/cpp_stl_98.html
+++ b/ipv6_packet/cpp_stl_98.html
@@ -441,7 +441,7 @@ <h3>ipv6_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/csharp.html b/ipv6_packet/csharp.html
index ff79d95cb..ef6d4b19b 100644
--- a/ipv6_packet/csharp.html
+++ b/ipv6_packet/csharp.html
@@ -350,7 +350,7 @@ <h3>Ipv6Packet.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/go.html b/ipv6_packet/go.html
index 3e5b54e14..1704c3c35 100644
--- a/ipv6_packet/go.html
+++ b/ipv6_packet/go.html
@@ -335,7 +335,7 @@ <h3>ipv6_packet.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/graphviz.html b/ipv6_packet/graphviz.html
index b3ae1c781..789c5b8bc 100644
--- a/ipv6_packet/graphviz.html
+++ b/ipv6_packet/graphviz.html
@@ -272,7 +272,7 @@ <h3>ipv6_packet.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/index.html b/ipv6_packet/index.html
index 3d5609059..decc85e8b 100644
--- a/ipv6_packet/index.html
+++ b/ipv6_packet/index.html
@@ -265,7 +265,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/java.html b/ipv6_packet/java.html
index 9bde91364..f68bda942 100644
--- a/ipv6_packet/java.html
+++ b/ipv6_packet/java.html
@@ -357,7 +357,7 @@ <h3>Ipv6Packet.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/javascript.html b/ipv6_packet/javascript.html
index cddf82901..897360ee0 100644
--- a/ipv6_packet/javascript.html
+++ b/ipv6_packet/javascript.html
@@ -325,7 +325,7 @@ <h3>Ipv6Packet.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/lua.html b/ipv6_packet/lua.html
index 8d491b9e3..1b876e11d 100644
--- a/ipv6_packet/lua.html
+++ b/ipv6_packet/lua.html
@@ -279,7 +279,7 @@ <h3>ipv6_packet.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/nim.html b/ipv6_packet/nim.html
index 101888f4d..e400f296a 100644
--- a/ipv6_packet/nim.html
+++ b/ipv6_packet/nim.html
@@ -303,7 +303,7 @@ <h3>ipv6_packet.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/perl.html b/ipv6_packet/perl.html
index f2a015a23..d82558e66 100644
--- a/ipv6_packet/perl.html
+++ b/ipv6_packet/perl.html
@@ -350,7 +350,7 @@ <h3>Ipv6Packet.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/php.html b/ipv6_packet/php.html
index 6d633b6b6..65ce20f98 100644
--- a/ipv6_packet/php.html
+++ b/ipv6_packet/php.html
@@ -294,7 +294,7 @@ <h3>Ipv6Packet.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/python.html b/ipv6_packet/python.html
index 33663e661..a7827a519 100644
--- a/ipv6_packet/python.html
+++ b/ipv6_packet/python.html
@@ -322,7 +322,7 @@ <h3>ipv6_packet.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ipv6_packet/ruby.html b/ipv6_packet/ruby.html
index e752a229a..eaca39542 100644
--- a/ipv6_packet/ruby.html
+++ b/ipv6_packet/ruby.html
@@ -330,7 +330,7 @@ <h3>ipv6_packet.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/cpp_stl_11.html b/iso9660/cpp_stl_11.html
index 50e0a2505..d7229d719 100644
--- a/iso9660/cpp_stl_11.html
+++ b/iso9660/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1428,7 +1428,7 @@ <h3>iso9660.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/cpp_stl_98.html b/iso9660/cpp_stl_98.html
index bb5f28bfb..869c90892 100644
--- a/iso9660/cpp_stl_98.html
+++ b/iso9660/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1592,7 +1592,7 @@ <h3>iso9660.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/csharp.html b/iso9660/csharp.html
index 21b00f338..a708502b6 100644
--- a/iso9660/csharp.html
+++ b/iso9660/csharp.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1007,7 +1007,7 @@ <h3>Iso9660.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/go.html b/iso9660/go.html
index b630bb1b4..c68c3e8db 100644
--- a/iso9660/go.html
+++ b/iso9660/go.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1265,7 +1265,7 @@ <h3>iso9660.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/graphviz.html b/iso9660/graphviz.html
index 702b7190d..b05f2ffa0 100644
--- a/iso9660/graphviz.html
+++ b/iso9660/graphviz.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -527,7 +527,7 @@ <h3>iso9660.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/index.html b/iso9660/index.html
index acfb73589..496eaf77a 100644
--- a/iso9660/index.html
+++ b/iso9660/index.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -547,7 +547,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/java.html b/iso9660/java.html
index e8fbad88e..4d667b201 100644
--- a/iso9660/java.html
+++ b/iso9660/java.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1039,7 +1039,7 @@ <h3>Iso9660.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/javascript.html b/iso9660/javascript.html
index 5ab570347..15fec12ea 100644
--- a/iso9660/javascript.html
+++ b/iso9660/javascript.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>Iso9660.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/lua.html b/iso9660/lua.html
index 54e616ffe..2f9800b25 100644
--- a/iso9660/lua.html
+++ b/iso9660/lua.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -665,7 +665,7 @@ <h3>iso9660.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/nim.html b/iso9660/nim.html
index 599d77438..5fcca1005 100644
--- a/iso9660/nim.html
+++ b/iso9660/nim.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -843,7 +843,7 @@ <h3>iso9660.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/perl.html b/iso9660/perl.html
index f844fa2b6..96f2be624 100644
--- a/iso9660/perl.html
+++ b/iso9660/perl.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -1268,7 +1268,7 @@ <h3>Iso9660.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/php.html b/iso9660/php.html
index 80004fd63..77e6bd940 100644
--- a/iso9660/php.html
+++ b/iso9660/php.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -787,7 +787,7 @@ <h3>Iso9660.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/python.html b/iso9660/python.html
index 343c6a837..5ec2f7109 100644
--- a/iso9660/python.html
+++ b/iso9660/python.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -661,7 +661,7 @@ <h3>iso9660.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/iso9660/ruby.html b/iso9660/ruby.html
index 03de3f743..5bb3872d8 100644
--- a/iso9660/ruby.html
+++ b/iso9660/ruby.html
@@ -105,13 +105,13 @@ <h1>ISO9660 CD filesystem:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ISO9660 is standard filesystem used on read-only optical discs
-(mostly CD-ROM). The standard was based on earlier High Sierra
-Format (HSF), proposed for CD-ROMs in 1985, and, after several
+                <p><p>ISO9660 is standard filesystem used on read-only optical discs<br />
+(mostly CD-ROM). The standard was based on earlier High Sierra<br />
+Format (HSF), proposed for CD-ROMs in 1985, and, after several<br />
 revisions, it was accepted as ISO9960:1998.</p>
-<p>The format emphasizes portability (thus having pretty minimal
-features and very conservative file names standards) and sequential
-access (which favors disc devices with relatively slow rotation
+<p>The format emphasizes portability (thus having pretty minimal<br />
+features and very conservative file names standards) and sequential<br />
+access (which favors disc devices with relatively slow rotation<br />
 speed).</p>
 </p>
             </div>
@@ -718,7 +718,7 @@ <h3>iso9660.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/cpp_stl_11.html b/java_class/cpp_stl_11.html
index fdf2e4573..a5cb3d552 100644
--- a/java_class/cpp_stl_11.html
+++ b/java_class/cpp_stl_11.html
@@ -2508,7 +2508,7 @@ <h3>java_class.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/cpp_stl_98.html b/java_class/cpp_stl_98.html
index b1b3dcfe0..2b7dbe15b 100644
--- a/java_class/cpp_stl_98.html
+++ b/java_class/cpp_stl_98.html
@@ -2771,7 +2771,7 @@ <h3>java_class.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/csharp.html b/java_class/csharp.html
index 59d055bfb..45164e227 100644
--- a/java_class/csharp.html
+++ b/java_class/csharp.html
@@ -1820,7 +1820,7 @@ <h3>JavaClass.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/index.html b/java_class/index.html
index e3d1d17cc..c86365753 100644
--- a/java_class/index.html
+++ b/java_class/index.html
@@ -737,7 +737,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/java.html b/java_class/java.html
index 3f2f672cd..5ca2b5637 100644
--- a/java_class/java.html
+++ b/java_class/java.html
@@ -1814,7 +1814,7 @@ <h3>JavaClass.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/javascript.html b/java_class/javascript.html
index 92a5b98fa..ee30824c8 100644
--- a/java_class/javascript.html
+++ b/java_class/javascript.html
@@ -1299,7 +1299,7 @@ <h3>JavaClass.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/lua.html b/java_class/lua.html
index e22f1521c..ac4725cf2 100644
--- a/java_class/lua.html
+++ b/java_class/lua.html
@@ -1160,7 +1160,7 @@ <h3>java_class.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/php.html b/java_class/php.html
index de232b4b2..eb315771d 100644
--- a/java_class/php.html
+++ b/java_class/php.html
@@ -1216,7 +1216,7 @@ <h3>JavaClass.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/python.html b/java_class/python.html
index 6fee1b9a4..2444b34d0 100644
--- a/java_class/python.html
+++ b/java_class/python.html
@@ -1127,7 +1127,7 @@ <h3>java_class.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/java_class/ruby.html b/java_class/ruby.html
index 8b5a631c1..5a3d1f8dc 100644
--- a/java_class/ruby.html
+++ b/java_class/ruby.html
@@ -1115,7 +1115,7 @@ <h3>java_class.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/cpp_stl_11.html b/jpeg/cpp_stl_11.html
index 9e77451cf..976c4dcec 100644
--- a/jpeg/cpp_stl_11.html
+++ b/jpeg/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -1136,7 +1136,7 @@ <h3>jpeg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/cpp_stl_98.html b/jpeg/cpp_stl_98.html
index ae4be6224..202830e91 100644
--- a/jpeg/cpp_stl_98.html
+++ b/jpeg/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -1225,7 +1225,7 @@ <h3>jpeg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/csharp.html b/jpeg/csharp.html
index 6cb4e32af..989ed135a 100644
--- a/jpeg/csharp.html
+++ b/jpeg/csharp.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -851,7 +851,7 @@ <h3>Jpeg.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/go.html b/jpeg/go.html
index a80074700..7cfdd8c4b 100644
--- a/jpeg/go.html
+++ b/jpeg/go.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -907,7 +907,7 @@ <h3>jpeg.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/graphviz.html b/jpeg/graphviz.html
index 35301e608..a217fb066 100644
--- a/jpeg/graphviz.html
+++ b/jpeg/graphviz.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -445,7 +445,7 @@ <h3>jpeg.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/index.html b/jpeg/index.html
index 0b128f901..844232829 100644
--- a/jpeg/index.html
+++ b/jpeg/index.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -504,7 +504,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/java.html b/jpeg/java.html
index d07c4caf2..77120bb05 100644
--- a/jpeg/java.html
+++ b/jpeg/java.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -921,7 +921,7 @@ <h3>Jpeg.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/javascript.html b/jpeg/javascript.html
index ac173841f..23f9360e8 100644
--- a/jpeg/javascript.html
+++ b/jpeg/javascript.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -735,7 +735,7 @@ <h3>Jpeg.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/lua.html b/jpeg/lua.html
index 6c5b57dd3..f80269331 100644
--- a/jpeg/lua.html
+++ b/jpeg/lua.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -613,7 +613,7 @@ <h3>jpeg.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/nim.html b/jpeg/nim.html
index 4d0c9ab02..c41cce6f9 100644
--- a/jpeg/nim.html
+++ b/jpeg/nim.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -717,7 +717,7 @@ <h3>jpeg.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/perl.html b/jpeg/perl.html
index c76dc53fa..37e987f3c 100644
--- a/jpeg/perl.html
+++ b/jpeg/perl.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -908,7 +908,7 @@ <h3>Jpeg.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/php.html b/jpeg/php.html
index 88009684d..3a47f3411 100644
--- a/jpeg/php.html
+++ b/jpeg/php.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -702,7 +702,7 @@ <h3>Jpeg.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/python.html b/jpeg/python.html
index 6e1f3c54e..22fe4e1ad 100644
--- a/jpeg/python.html
+++ b/jpeg/python.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -593,7 +593,7 @@ <h3>jpeg.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/jpeg/ruby.html b/jpeg/ruby.html
index 1eefe1abd..d3775e5d2 100644
--- a/jpeg/ruby.html
+++ b/jpeg/ruby.html
@@ -105,12 +105,12 @@ <h1>JPEG (Joint Photographic Experts Group) File Interchange Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known
-as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,
-offering lossy compression which works reasonably well with
+                <p><p>JPEG File Interchange Format, or JFIF, or, more colloquially known<br />
+as just &quot;JPEG&quot; or &quot;JPG&quot;, is a popular 2D bitmap image file format,<br />
+offering lossy compression which works reasonably well with<br />
 photographic images.</p>
-<p>Format is organized as a container format, serving multiple
-&quot;segments&quot;, each starting with a magic and a marker. JFIF standard
+<p>Format is organized as a container format, serving multiple<br />
+&quot;segments&quot;, each starting with a magic and a marker. JFIF standard<br />
 dictates order and mandatory apperance of segments:</p>
 <ul>
 <li>SOI</li>
@@ -664,7 +664,7 @@ <h3>jpeg.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/cpp_stl_11.html b/luks/cpp_stl_11.html
index 6a3ba0477..7a2296cbe 100644
--- a/luks/cpp_stl_11.html
+++ b/luks/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -617,7 +617,7 @@ <h3>luks.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/cpp_stl_98.html b/luks/cpp_stl_98.html
index 485680f41..f6ee88b91 100644
--- a/luks/cpp_stl_98.html
+++ b/luks/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -646,7 +646,7 @@ <h3>luks.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/csharp.html b/luks/csharp.html
index da7b8c9b0..731e1f8bc 100644
--- a/luks/csharp.html
+++ b/luks/csharp.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -497,7 +497,7 @@ <h3>Luks.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/go.html b/luks/go.html
index 77d67e800..2f8d4bf6c 100644
--- a/luks/go.html
+++ b/luks/go.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -526,7 +526,7 @@ <h3>luks.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/graphviz.html b/luks/graphviz.html
index 6207a169d..1c33e5633 100644
--- a/luks/graphviz.html
+++ b/luks/graphviz.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -332,7 +332,7 @@ <h3>luks.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/index.html b/luks/index.html
index 90d808ebd..18271895a 100644
--- a/luks/index.html
+++ b/luks/index.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -337,7 +337,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/java.html b/luks/java.html
index 8c4d3ff36..c9c421d1b 100644
--- a/luks/java.html
+++ b/luks/java.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -509,7 +509,7 @@ <h3>Luks.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/javascript.html b/luks/javascript.html
index 83e5e8d75..e3e1e3cd0 100644
--- a/luks/javascript.html
+++ b/luks/javascript.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -427,7 +427,7 @@ <h3>Luks.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/lua.html b/luks/lua.html
index 90d7c074e..0b4dd85d1 100644
--- a/luks/lua.html
+++ b/luks/lua.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -379,7 +379,7 @@ <h3>luks.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/nim.html b/luks/nim.html
index 453d56998..181673ec2 100644
--- a/luks/nim.html
+++ b/luks/nim.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -415,7 +415,7 @@ <h3>luks.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/perl.html b/luks/perl.html
index f67476df3..7976f67cb 100644
--- a/luks/perl.html
+++ b/luks/perl.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -510,7 +510,7 @@ <h3>Luks.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/php.html b/luks/php.html
index b1b507d15..fa6db8a6e 100644
--- a/luks/php.html
+++ b/luks/php.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -405,7 +405,7 @@ <h3>Luks.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/python.html b/luks/python.html
index c89800ea5..526b2c28f 100644
--- a/luks/python.html
+++ b/luks/python.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -410,7 +410,7 @@ <h3>luks.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/luks/ruby.html b/luks/ruby.html
index 9203919b9..d950d4209 100644
--- a/luks/ruby.html
+++ b/luks/ruby.html
@@ -105,7 +105,7 @@ <h1>Linux Unified Key Setup:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk
+                <p><p>Linux Unified Key Setup (LUKS) is a format specification for storing disk<br />
 encryption parameters and up to 8 user keys (which can unlock the master key).</p>
 </p>
             </div>
@@ -419,7 +419,7 @@ <h3>luks.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/cpp_stl_11.html b/lvm2/cpp_stl_11.html
index e597bb509..142838384 100644
--- a/lvm2/cpp_stl_11.html
+++ b/lvm2/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -1166,7 +1166,7 @@ <h3>lvm2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/cpp_stl_98.html b/lvm2/cpp_stl_98.html
index 4c01971a3..fb25002ec 100644
--- a/lvm2/cpp_stl_98.html
+++ b/lvm2/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -1279,7 +1279,7 @@ <h3>lvm2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/csharp.html b/lvm2/csharp.html
index abc30dff8..6b2aa8a52 100644
--- a/lvm2/csharp.html
+++ b/lvm2/csharp.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -863,7 +863,7 @@ <h3>Lvm2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/go.html b/lvm2/go.html
index da3085d9f..1202dec65 100644
--- a/lvm2/go.html
+++ b/lvm2/go.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -906,7 +906,7 @@ <h3>lvm2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/graphviz.html b/lvm2/graphviz.html
index e0651e998..9db912cce 100644
--- a/lvm2/graphviz.html
+++ b/lvm2/graphviz.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -450,7 +450,7 @@ <h3>lvm2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/index.html b/lvm2/index.html
index 102d62f2f..b1ae4c98c 100644
--- a/lvm2/index.html
+++ b/lvm2/index.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -443,7 +443,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/java.html b/lvm2/java.html
index 41985a51b..9bf42e440 100644
--- a/lvm2/java.html
+++ b/lvm2/java.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -902,7 +902,7 @@ <h3>Lvm2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/javascript.html b/lvm2/javascript.html
index 805a8f1d3..10d581681 100644
--- a/lvm2/javascript.html
+++ b/lvm2/javascript.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -689,7 +689,7 @@ <h3>Lvm2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/lua.html b/lvm2/lua.html
index 05ca09a90..3c4e51879 100644
--- a/lvm2/lua.html
+++ b/lvm2/lua.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -611,7 +611,7 @@ <h3>lvm2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/nim.html b/lvm2/nim.html
index b6f2261c4..b25f570f5 100644
--- a/lvm2/nim.html
+++ b/lvm2/nim.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -717,7 +717,7 @@ <h3>lvm2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/perl.html b/lvm2/perl.html
index 1e203e65f..95df29239 100644
--- a/lvm2/perl.html
+++ b/lvm2/perl.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -886,7 +886,7 @@ <h3>Lvm2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/php.html b/lvm2/php.html
index 631e9885e..88363650a 100644
--- a/lvm2/php.html
+++ b/lvm2/php.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -675,7 +675,7 @@ <h3>Lvm2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/python.html b/lvm2/python.html
index 4ab1a4898..9f91a7b6b 100644
--- a/lvm2/python.html
+++ b/lvm2/python.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -569,7 +569,7 @@ <h3>lvm2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lvm2/ruby.html b/lvm2/ruby.html
index 78a5dfa25..59e84803e 100644
--- a/lvm2/ruby.html
+++ b/lvm2/ruby.html
@@ -105,14 +105,14 @@ <h1>Logical Volume Manager version 2:
 
         <div class="row">
             <div class="col-md-8">
-                <p><h3>Building a test file</h3>
-<pre><code>dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
-sudo losetup /dev/loop1 image.img
-sudo pvcreate /dev/loop1
-sudo vgcreate vg_test /dev/loop1
-sudo lvcreate --name lv_test1 vg_test
-sudo losetup -d /dev/loop1
-</code></pre>
+                <p><h3><a href="#building-a-test-file" aria-hidden="true" class="anchor" id="building-a-test-file"></a>Building a test file</h3>
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">dd if=/dev/zero of=image.img bs=512 count=$(( 4 * 1024 * 2 ))
+</span><span style="color:#c0c5ce;">sudo losetup /dev/loop1 image.img
+</span><span style="color:#c0c5ce;">sudo pvcreate /dev/loop1
+</span><span style="color:#c0c5ce;">sudo vgcreate vg_test /dev/loop1
+</span><span style="color:#c0c5ce;">sudo lvcreate --name lv_test1 vg_test
+</span><span style="color:#c0c5ce;">sudo losetup -d /dev/loop1
+</span></code></pre>
 </p>
             </div>
             <div class="col-md-4">
@@ -636,7 +636,7 @@ <h3>lvm2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/cpp_stl_11.html b/lzh/cpp_stl_11.html
index ef89eb53d..d860c6ee4 100644
--- a/lzh/cpp_stl_11.html
+++ b/lzh/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -792,7 +792,7 @@ <h3>lzh.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/cpp_stl_98.html b/lzh/cpp_stl_98.html
index f248406c5..df0378ca6 100644
--- a/lzh/cpp_stl_98.html
+++ b/lzh/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -848,7 +848,7 @@ <h3>lzh.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/csharp.html b/lzh/csharp.html
index a892bb73a..2766ade17 100644
--- a/lzh/csharp.html
+++ b/lzh/csharp.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -559,7 +559,7 @@ <h3>Lzh.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/go.html b/lzh/go.html
index 0ede03ebe..5c7d8fa6f 100644
--- a/lzh/go.html
+++ b/lzh/go.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -572,7 +572,7 @@ <h3>lzh.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/graphviz.html b/lzh/graphviz.html
index 8bacb657b..fbca220bc 100644
--- a/lzh/graphviz.html
+++ b/lzh/graphviz.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -361,7 +361,7 @@ <h3>lzh.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/index.html b/lzh/index.html
index 52392d6c7..b87bb040b 100644
--- a/lzh/index.html
+++ b/lzh/index.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -366,7 +366,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/java.html b/lzh/java.html
index 77cba8e46..fcfc4ca1f 100644
--- a/lzh/java.html
+++ b/lzh/java.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h3>Lzh.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/javascript.html b/lzh/javascript.html
index 8aa210e92..2fd85e35d 100644
--- a/lzh/javascript.html
+++ b/lzh/javascript.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -482,7 +482,7 @@ <h3>Lzh.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/lua.html b/lzh/lua.html
index 9c06c15a1..739c81fb3 100644
--- a/lzh/lua.html
+++ b/lzh/lua.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -423,7 +423,7 @@ <h3>lzh.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/nim.html b/lzh/nim.html
index 780142e57..09c0f81db 100644
--- a/lzh/nim.html
+++ b/lzh/nim.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -480,7 +480,7 @@ <h3>lzh.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/perl.html b/lzh/perl.html
index 8152e316c..5e34f057e 100644
--- a/lzh/perl.html
+++ b/lzh/perl.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -603,7 +603,7 @@ <h3>Lzh.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/php.html b/lzh/php.html
index d5a861f6e..f8fdbe865 100644
--- a/lzh/php.html
+++ b/lzh/php.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -465,7 +465,7 @@ <h3>Lzh.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/python.html b/lzh/python.html
index 10b4bded0..f49a3cb0d 100644
--- a/lzh/python.html
+++ b/lzh/python.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -440,7 +440,7 @@ <h3>lzh.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/lzh/ruby.html b/lzh/ruby.html
index 0ccd34253..f52715b35 100644
--- a/lzh/ruby.html
+++ b/lzh/ruby.html
@@ -105,11 +105,11 @@ <h1>.lzh file format of LHA (AKA LHarc) by Yoshizaki Haruyasu:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware
-eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the
-years, many ports and implementations were developed, sporting many
+                <p><p>LHA (LHarc, LZH) is a file format used by a popular freeware<br />
+eponymous archiver, created in 1988 by Haruyasu Yoshizaki. Over the<br />
+years, many ports and implementations were developed, sporting many<br />
 extensions to original 1988 LZH.</p>
-<p>File format is pretty simple and essentially consists of a stream of
+<p>File format is pretty simple and essentially consists of a stream of<br />
 records.</p>
 </p>
             </div>
@@ -476,7 +476,7 @@ <h3>lzh.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/cpp_stl_11.html b/mac_os_resource_snd/cpp_stl_11.html
index e77cd0bce..196905f02 100644
--- a/mac_os_resource_snd/cpp_stl_11.html
+++ b/mac_os_resource_snd/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -1445,7 +1445,7 @@ <h3>mac_os_resource_snd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/csharp.html b/mac_os_resource_snd/csharp.html
index 69d785696..8b02c0bbc 100644
--- a/mac_os_resource_snd/csharp.html
+++ b/mac_os_resource_snd/csharp.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -1080,7 +1080,7 @@ <h3>MacOsResourceSnd.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/go.html b/mac_os_resource_snd/go.html
index 8abc7e3e0..240858d04 100644
--- a/mac_os_resource_snd/go.html
+++ b/mac_os_resource_snd/go.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -1191,7 +1191,7 @@ <h3>mac_os_resource_snd.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/graphviz.html b/mac_os_resource_snd/graphviz.html
index adb3d4972..23cd0029f 100644
--- a/mac_os_resource_snd/graphviz.html
+++ b/mac_os_resource_snd/graphviz.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -475,7 +475,7 @@ <h3>mac_os_resource_snd.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/index.html b/mac_os_resource_snd/index.html
index 9c97c2ea4..eb55d2ae6 100644
--- a/mac_os_resource_snd/index.html
+++ b/mac_os_resource_snd/index.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -710,7 +710,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/java.html b/mac_os_resource_snd/java.html
index eda9d9268..49927bf1e 100644
--- a/mac_os_resource_snd/java.html
+++ b/mac_os_resource_snd/java.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -1073,7 +1073,7 @@ <h3>MacOsResourceSnd.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/javascript.html b/mac_os_resource_snd/javascript.html
index 7fdad2aad..0d34576c0 100644
--- a/mac_os_resource_snd/javascript.html
+++ b/mac_os_resource_snd/javascript.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -897,7 +897,7 @@ <h3>MacOsResourceSnd.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/lua.html b/mac_os_resource_snd/lua.html
index 88783e5bd..17781f8ea 100644
--- a/mac_os_resource_snd/lua.html
+++ b/mac_os_resource_snd/lua.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -759,7 +759,7 @@ <h3>mac_os_resource_snd.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/nim.html b/mac_os_resource_snd/nim.html
index 61d8fdcd5..2c07059f2 100644
--- a/mac_os_resource_snd/nim.html
+++ b/mac_os_resource_snd/nim.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -901,7 +901,7 @@ <h3>mac_os_resource_snd.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/perl.html b/mac_os_resource_snd/perl.html
index 5cf7ab8af..87ad95984 100644
--- a/mac_os_resource_snd/perl.html
+++ b/mac_os_resource_snd/perl.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -991,7 +991,7 @@ <h3>MacOsResourceSnd.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/php.html b/mac_os_resource_snd/php.html
index 55f5f8a35..aaf1dfbb3 100644
--- a/mac_os_resource_snd/php.html
+++ b/mac_os_resource_snd/php.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -1012,7 +1012,7 @@ <h3>MacOsResourceSnd.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/python.html b/mac_os_resource_snd/python.html
index b20bf430a..3f0c7e8fe 100644
--- a/mac_os_resource_snd/python.html
+++ b/mac_os_resource_snd/python.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -697,7 +697,7 @@ <h3>mac_os_resource_snd.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mac_os_resource_snd/ruby.html b/mac_os_resource_snd/ruby.html
index 4bbfb437b..e8f2aab2f 100644
--- a/mac_os_resource_snd/ruby.html
+++ b/mac_os_resource_snd/ruby.html
@@ -105,8 +105,8 @@ <h1>Classic MacOS Sound Resource:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.
-They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.
+                <p><p>Sound resources were introduced in Classic MacOS with the Sound Manager program.<br />
+They can contain sound commands to generate sounds with given frequencies as well as sampled sound data.<br />
 They are mostly found in resource forks, but can occasionally appear standalone or embedded in other files.</p>
 </p>
             </div>
@@ -778,7 +778,7 @@ <h3>mac_os_resource_snd.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/cpp_stl_11.html b/mach_o/cpp_stl_11.html
index c0196f7df..fd3655b9d 100644
--- a/mach_o/cpp_stl_11.html
+++ b/mach_o/cpp_stl_11.html
@@ -6448,7 +6448,7 @@ <h3>mach_o.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/cpp_stl_98.html b/mach_o/cpp_stl_98.html
index 0d122952a..4025d647b 100644
--- a/mach_o/cpp_stl_98.html
+++ b/mach_o/cpp_stl_98.html
@@ -7167,7 +7167,7 @@ <h3>mach_o.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/csharp.html b/mach_o/csharp.html
index 77d98b148..f90ce8dfb 100644
--- a/mach_o/csharp.html
+++ b/mach_o/csharp.html
@@ -4434,7 +4434,7 @@ <h3>MachO.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/go.html b/mach_o/go.html
index bb9663faf..ff71b03cf 100644
--- a/mach_o/go.html
+++ b/mach_o/go.html
@@ -5757,7 +5757,7 @@ <h3>mach_o.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/graphviz.html b/mach_o/graphviz.html
index 17b5decb8..68ed8096b 100644
--- a/mach_o/graphviz.html
+++ b/mach_o/graphviz.html
@@ -1688,7 +1688,7 @@ <h3>mach_o.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/index.html b/mach_o/index.html
index e858726fa..2cef20267 100644
--- a/mach_o/index.html
+++ b/mach_o/index.html
@@ -1652,7 +1652,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/java.html b/mach_o/java.html
index 46d0f6a34..72bbd994f 100644
--- a/mach_o/java.html
+++ b/mach_o/java.html
@@ -4576,7 +4576,7 @@ <h3>MachO.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/javascript.html b/mach_o/javascript.html
index 9205afb8a..62297e478 100644
--- a/mach_o/javascript.html
+++ b/mach_o/javascript.html
@@ -3118,7 +3118,7 @@ <h3>MachO.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/lua.html b/mach_o/lua.html
index 013ebebb0..75a6117be 100644
--- a/mach_o/lua.html
+++ b/mach_o/lua.html
@@ -2795,7 +2795,7 @@ <h3>mach_o.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/nim.html b/mach_o/nim.html
index 4fb36e3e9..062f8e6d1 100644
--- a/mach_o/nim.html
+++ b/mach_o/nim.html
@@ -3646,7 +3646,7 @@ <h3>mach_o.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/perl.html b/mach_o/perl.html
index fae3e951d..c8e8f8e73 100644
--- a/mach_o/perl.html
+++ b/mach_o/perl.html
@@ -5328,7 +5328,7 @@ <h3>MachO.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/php.html b/mach_o/php.html
index 5835c98d2..a82451f24 100644
--- a/mach_o/php.html
+++ b/mach_o/php.html
@@ -3267,7 +3267,7 @@ <h3>MachO.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/python.html b/mach_o/python.html
index eb49f6047..d8ea989f5 100644
--- a/mach_o/python.html
+++ b/mach_o/python.html
@@ -2477,7 +2477,7 @@ <h3>mach_o.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o/ruby.html b/mach_o/ruby.html
index 288d08315..ff8c4d162 100644
--- a/mach_o/ruby.html
+++ b/mach_o/ruby.html
@@ -2666,7 +2666,7 @@ <h3>mach_o.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/cpp_stl_11.html b/mach_o_fat/cpp_stl_11.html
index 4399b3863..22062495d 100644
--- a/mach_o_fat/cpp_stl_11.html
+++ b/mach_o_fat/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -506,7 +506,7 @@ <h3>mach_o_fat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/cpp_stl_98.html b/mach_o_fat/cpp_stl_98.html
index 5c00a6083..8465d3d4f 100644
--- a/mach_o_fat/cpp_stl_98.html
+++ b/mach_o_fat/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -532,7 +532,7 @@ <h3>mach_o_fat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/csharp.html b/mach_o_fat/csharp.html
index bb0c5956d..8e9fc6b5c 100644
--- a/mach_o_fat/csharp.html
+++ b/mach_o_fat/csharp.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -401,7 +401,7 @@ <h3>MachOFat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/go.html b/mach_o_fat/go.html
index 5b95d32ce..b244c76a4 100644
--- a/mach_o_fat/go.html
+++ b/mach_o_fat/go.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -389,7 +389,7 @@ <h3>mach_o_fat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/graphviz.html b/mach_o_fat/graphviz.html
index 3910f0fac..c9b73bb96 100644
--- a/mach_o_fat/graphviz.html
+++ b/mach_o_fat/graphviz.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -286,7 +286,7 @@ <h3>mach_o_fat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/index.html b/mach_o_fat/index.html
index 7e445a062..1b225b966 100644
--- a/mach_o_fat/index.html
+++ b/mach_o_fat/index.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -285,7 +285,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/java.html b/mach_o_fat/java.html
index d2fecd39a..99e43641a 100644
--- a/mach_o_fat/java.html
+++ b/mach_o_fat/java.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -404,7 +404,7 @@ <h3>MachOFat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/javascript.html b/mach_o_fat/javascript.html
index 489822154..93a7607b8 100644
--- a/mach_o_fat/javascript.html
+++ b/mach_o_fat/javascript.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -361,7 +361,7 @@ <h3>MachOFat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/lua.html b/mach_o_fat/lua.html
index d96494d84..0aee2fef9 100644
--- a/mach_o_fat/lua.html
+++ b/mach_o_fat/lua.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -315,7 +315,7 @@ <h3>mach_o_fat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/nim.html b/mach_o_fat/nim.html
index 80c29594f..434b3320c 100644
--- a/mach_o_fat/nim.html
+++ b/mach_o_fat/nim.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -337,7 +337,7 @@ <h3>mach_o_fat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/perl.html b/mach_o_fat/perl.html
index 2abf17dac..51ee24152 100644
--- a/mach_o_fat/perl.html
+++ b/mach_o_fat/perl.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -389,7 +389,7 @@ <h3>MachOFat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/php.html b/mach_o_fat/php.html
index 3aa1f9af9..5a7d09422 100644
--- a/mach_o_fat/php.html
+++ b/mach_o_fat/php.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -325,7 +325,7 @@ <h3>MachOFat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/python.html b/mach_o_fat/python.html
index 5bd00ca8b..88126fd42 100644
--- a/mach_o_fat/python.html
+++ b/mach_o_fat/python.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -352,7 +352,7 @@ <h3>mach_o_fat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mach_o_fat/ruby.html b/mach_o_fat/ruby.html
index 83d2eaa16..e1b6c40de 100644
--- a/mach_o_fat/ruby.html
+++ b/mach_o_fat/ruby.html
@@ -105,8 +105,8 @@ <h1>macOS Mach-O multiarch ("fat") binary:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This is a simple container format that encapsulates multiple Mach-O files,
-each generally for a different architecture. XNU can execute these files just
+                <p><p>This is a simple container format that encapsulates multiple Mach-O files,<br />
+each generally for a different architecture. XNU can execute these files just<br />
 like single-arch Mach-Os and will pick the appropriate entry.</p>
 </p>
             </div>
@@ -355,7 +355,7 @@ <h3>mach_o_fat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/cpp_stl_11.html b/magicavoxel_vox/cpp_stl_11.html
index 676d7d4eb..abb2507a2 100644
--- a/magicavoxel_vox/cpp_stl_11.html
+++ b/magicavoxel_vox/cpp_stl_11.html
@@ -1211,7 +1211,7 @@ <h3>magicavoxel_vox.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/cpp_stl_98.html b/magicavoxel_vox/cpp_stl_98.html
index 2392ec11d..b4e412168 100644
--- a/magicavoxel_vox/cpp_stl_98.html
+++ b/magicavoxel_vox/cpp_stl_98.html
@@ -1294,7 +1294,7 @@ <h3>magicavoxel_vox.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/csharp.html b/magicavoxel_vox/csharp.html
index e4cc5fc03..999b8df04 100644
--- a/magicavoxel_vox/csharp.html
+++ b/magicavoxel_vox/csharp.html
@@ -859,7 +859,7 @@ <h3>MagicavoxelVox.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/go.html b/magicavoxel_vox/go.html
index 23fad157a..749091a9e 100644
--- a/magicavoxel_vox/go.html
+++ b/magicavoxel_vox/go.html
@@ -926,7 +926,7 @@ <h3>magicavoxel_vox.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/graphviz.html b/magicavoxel_vox/graphviz.html
index 300d66a3d..fbd6d35b2 100644
--- a/magicavoxel_vox/graphviz.html
+++ b/magicavoxel_vox/graphviz.html
@@ -461,7 +461,7 @@ <h3>magicavoxel_vox.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/index.html b/magicavoxel_vox/index.html
index 4da4d79e2..a6c913f63 100644
--- a/magicavoxel_vox/index.html
+++ b/magicavoxel_vox/index.html
@@ -464,7 +464,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/java.html b/magicavoxel_vox/java.html
index 6f7215804..62fd0f445 100644
--- a/magicavoxel_vox/java.html
+++ b/magicavoxel_vox/java.html
@@ -891,7 +891,7 @@ <h3>MagicavoxelVox.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/javascript.html b/magicavoxel_vox/javascript.html
index 6a5d515bb..0737efb1d 100644
--- a/magicavoxel_vox/javascript.html
+++ b/magicavoxel_vox/javascript.html
@@ -683,7 +683,7 @@ <h3>MagicavoxelVox.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/lua.html b/magicavoxel_vox/lua.html
index 066d1f7e5..de289d627 100644
--- a/magicavoxel_vox/lua.html
+++ b/magicavoxel_vox/lua.html
@@ -615,7 +615,7 @@ <h3>magicavoxel_vox.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/nim.html b/magicavoxel_vox/nim.html
index 723521c42..79b41efe2 100644
--- a/magicavoxel_vox/nim.html
+++ b/magicavoxel_vox/nim.html
@@ -701,7 +701,7 @@ <h3>magicavoxel_vox.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/perl.html b/magicavoxel_vox/perl.html
index 0c35da270..fdc976997 100644
--- a/magicavoxel_vox/perl.html
+++ b/magicavoxel_vox/perl.html
@@ -933,7 +933,7 @@ <h3>MagicavoxelVox.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/php.html b/magicavoxel_vox/php.html
index 5a091d350..4975cd2a4 100644
--- a/magicavoxel_vox/php.html
+++ b/magicavoxel_vox/php.html
@@ -662,7 +662,7 @@ <h3>MagicavoxelVox.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/python.html b/magicavoxel_vox/python.html
index 18e00f6ab..1086b1a72 100644
--- a/magicavoxel_vox/python.html
+++ b/magicavoxel_vox/python.html
@@ -614,7 +614,7 @@ <h3>magicavoxel_vox.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/magicavoxel_vox/ruby.html b/magicavoxel_vox/ruby.html
index f0ebf600e..6c1750ef0 100644
--- a/magicavoxel_vox/ruby.html
+++ b/magicavoxel_vox/ruby.html
@@ -630,7 +630,7 @@ <h3>magicavoxel_vox.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/cpp_stl_11.html b/mbr_partition_table/cpp_stl_11.html
index 59c6ca191..dfb185b66 100644
--- a/mbr_partition_table/cpp_stl_11.html
+++ b/mbr_partition_table/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -594,7 +594,7 @@ <h3>mbr_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/cpp_stl_98.html b/mbr_partition_table/cpp_stl_98.html
index 225c95603..4301fb1d8 100644
--- a/mbr_partition_table/cpp_stl_98.html
+++ b/mbr_partition_table/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -626,7 +626,7 @@ <h3>mbr_partition_table.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/csharp.html b/mbr_partition_table/csharp.html
index 00dbe6aae..d8cef0276 100644
--- a/mbr_partition_table/csharp.html
+++ b/mbr_partition_table/csharp.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -473,7 +473,7 @@ <h3>MbrPartitionTable.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/go.html b/mbr_partition_table/go.html
index 6a7b8101a..88479e494 100644
--- a/mbr_partition_table/go.html
+++ b/mbr_partition_table/go.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -450,7 +450,7 @@ <h3>mbr_partition_table.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/graphviz.html b/mbr_partition_table/graphviz.html
index a9eb40369..3f070a45f 100644
--- a/mbr_partition_table/graphviz.html
+++ b/mbr_partition_table/graphviz.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -332,7 +332,7 @@ <h3>mbr_partition_table.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/index.html b/mbr_partition_table/index.html
index 11bcee697..46dd17497 100644
--- a/mbr_partition_table/index.html
+++ b/mbr_partition_table/index.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -322,7 +322,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/java.html b/mbr_partition_table/java.html
index 123cbbe49..7d221d5b4 100644
--- a/mbr_partition_table/java.html
+++ b/mbr_partition_table/java.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -478,7 +478,7 @@ <h3>MbrPartitionTable.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/javascript.html b/mbr_partition_table/javascript.html
index cc7d52024..83112ecdc 100644
--- a/mbr_partition_table/javascript.html
+++ b/mbr_partition_table/javascript.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -416,7 +416,7 @@ <h3>MbrPartitionTable.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/lua.html b/mbr_partition_table/lua.html
index 09a99a1aa..0974af33b 100644
--- a/mbr_partition_table/lua.html
+++ b/mbr_partition_table/lua.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -369,7 +369,7 @@ <h3>mbr_partition_table.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/nim.html b/mbr_partition_table/nim.html
index 8152e7121..68db4c8df 100644
--- a/mbr_partition_table/nim.html
+++ b/mbr_partition_table/nim.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -400,7 +400,7 @@ <h3>mbr_partition_table.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/perl.html b/mbr_partition_table/perl.html
index 127e8975d..6f7af9f7d 100644
--- a/mbr_partition_table/perl.html
+++ b/mbr_partition_table/perl.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -470,7 +470,7 @@ <h3>MbrPartitionTable.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/php.html b/mbr_partition_table/php.html
index c74b400f3..464e82590 100644
--- a/mbr_partition_table/php.html
+++ b/mbr_partition_table/php.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -384,7 +384,7 @@ <h3>MbrPartitionTable.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/python.html b/mbr_partition_table/python.html
index 2ad35aa52..f01b4d6c8 100644
--- a/mbr_partition_table/python.html
+++ b/mbr_partition_table/python.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -400,7 +400,7 @@ <h3>mbr_partition_table.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mbr_partition_table/ruby.html b/mbr_partition_table/ruby.html
index 82c3aef0c..a07908f07 100644
--- a/mbr_partition_table/ruby.html
+++ b/mbr_partition_table/ruby.html
@@ -105,13 +105,13 @@ <h1>MBR (Master Boot Record) partition table:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MBR (Master Boot Record) partition table is a traditional way of
-MS-DOS to partition larger hard disc drives into distinct
+                <p><p>MBR (Master Boot Record) partition table is a traditional way of<br />
+MS-DOS to partition larger hard disc drives into distinct<br />
 partitions.</p>
-<p>This table is stored in the end of the boot sector (first sector) of
-the drive, after the bootstrap code. Original DOS 2.0 specification
-allowed only 4 partitions per disc, but DOS 3.2 introduced concept
-of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;
+<p>This table is stored in the end of the boot sector (first sector) of<br />
+the drive, after the bootstrap code. Original DOS 2.0 specification<br />
+allowed only 4 partitions per disc, but DOS 3.2 introduced concept<br />
+of &quot;extended partitions&quot;, which work as nested extra &quot;boot records&quot;<br />
 which are pointed to by original (&quot;primary&quot;) partitions in MBR.</p>
 </p>
             </div>
@@ -406,7 +406,7 @@ <h3>mbr_partition_table.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/cpp_stl_11.html b/mcap/cpp_stl_11.html
index d9ec8a04c..a25e5d393 100644
--- a/mcap/cpp_stl_11.html
+++ b/mcap/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -2438,7 +2438,7 @@ <h3>mcap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/cpp_stl_98.html b/mcap/cpp_stl_98.html
index 10beb0d45..b0f179247 100644
--- a/mcap/cpp_stl_98.html
+++ b/mcap/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -2788,7 +2788,7 @@ <h3>mcap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/csharp.html b/mcap/csharp.html
index de09ca284..8848ebb64 100644
--- a/mcap/csharp.html
+++ b/mcap/csharp.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1670,7 +1670,7 @@ <h3>Mcap.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/go.html b/mcap/go.html
index 3c664f28a..b34b01df4 100644
--- a/mcap/go.html
+++ b/mcap/go.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -2158,7 +2158,7 @@ <h3>mcap.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/index.html b/mcap/index.html
index 6a66ac17f..686f09039 100644
--- a/mcap/index.html
+++ b/mcap/index.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -680,7 +680,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/java.html b/mcap/java.html
index 15a2adf42..d44905c0c 100644
--- a/mcap/java.html
+++ b/mcap/java.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1754,7 +1754,7 @@ <h3>Mcap.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/javascript.html b/mcap/javascript.html
index 6b0e9c549..e3e042515 100644
--- a/mcap/javascript.html
+++ b/mcap/javascript.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1156,7 +1156,7 @@ <h3>Mcap.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/lua.html b/mcap/lua.html
index 914f9dff4..7e1386909 100644
--- a/mcap/lua.html
+++ b/mcap/lua.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1068,7 +1068,7 @@ <h3>mcap.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/nim.html b/mcap/nim.html
index f83738fee..2ae1362a7 100644
--- a/mcap/nim.html
+++ b/mcap/nim.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1386,7 +1386,7 @@ <h3>mcap.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/perl.html b/mcap/perl.html
index 7a2a26d54..e1ba2c8a3 100644
--- a/mcap/perl.html
+++ b/mcap/perl.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -2110,7 +2110,7 @@ <h3>Mcap.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/php.html b/mcap/php.html
index a390d3d28..67ebb1b49 100644
--- a/mcap/php.html
+++ b/mcap/php.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1244,7 +1244,7 @@ <h3>Mcap.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/python.html b/mcap/python.html
index 54ff79d34..952c056df 100644
--- a/mcap/python.html
+++ b/mcap/python.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -983,7 +983,7 @@ <h3>mcap.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mcap/ruby.html b/mcap/ruby.html
index bd797cb7a..eb008f14b 100644
--- a/mcap/ruby.html
+++ b/mcap/ruby.html
@@ -105,12 +105,12 @@ <h1>MCAP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MCAP is a modular container format and logging library for pub/sub messages with
-arbitrary message serialization. It is primarily intended for use in robotics
-applications, and works well under various workloads, resource constraints, and
+                <p><p>MCAP is a modular container format and logging library for pub/sub messages with<br />
+arbitrary message serialization. It is primarily intended for use in robotics<br />
+applications, and works well under various workloads, resource constraints, and<br />
 durability requirements.</p>
-<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in
-nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,
+<p>Time values (<code>log_time</code>, <code>publish_time</code>, <code>create_time</code>) are represented in<br />
+nanoseconds since a user-understood epoch (i.e. Unix epoch, robot boot time,<br />
 etc.)</p>
 </p>
             </div>
@@ -1074,7 +1074,7 @@ <h3>mcap.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/cpp_stl_11.html b/microsoft_cfb/cpp_stl_11.html
index de426f6ae..c26438ba3 100644
--- a/microsoft_cfb/cpp_stl_11.html
+++ b/microsoft_cfb/cpp_stl_11.html
@@ -936,7 +936,7 @@ <h3>microsoft_cfb.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/cpp_stl_98.html b/microsoft_cfb/cpp_stl_98.html
index de85e72cb..9ffa149b0 100644
--- a/microsoft_cfb/cpp_stl_98.html
+++ b/microsoft_cfb/cpp_stl_98.html
@@ -989,7 +989,7 @@ <h3>microsoft_cfb.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/csharp.html b/microsoft_cfb/csharp.html
index e11afd064..ef13e7a27 100644
--- a/microsoft_cfb/csharp.html
+++ b/microsoft_cfb/csharp.html
@@ -739,7 +739,7 @@ <h3>MicrosoftCfb.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/go.html b/microsoft_cfb/go.html
index 20ae4b983..d8cdfa876 100644
--- a/microsoft_cfb/go.html
+++ b/microsoft_cfb/go.html
@@ -885,7 +885,7 @@ <h3>microsoft_cfb.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/graphviz.html b/microsoft_cfb/graphviz.html
index 06e3c9a5f..c4983f977 100644
--- a/microsoft_cfb/graphviz.html
+++ b/microsoft_cfb/graphviz.html
@@ -393,7 +393,7 @@ <h3>microsoft_cfb.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/index.html b/microsoft_cfb/index.html
index 6038c6aea..ad4f28c89 100644
--- a/microsoft_cfb/index.html
+++ b/microsoft_cfb/index.html
@@ -406,7 +406,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/java.html b/microsoft_cfb/java.html
index 6ab20c96d..b0dc0cf46 100644
--- a/microsoft_cfb/java.html
+++ b/microsoft_cfb/java.html
@@ -732,7 +732,7 @@ <h3>MicrosoftCfb.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/javascript.html b/microsoft_cfb/javascript.html
index b00833b92..0ada8c647 100644
--- a/microsoft_cfb/javascript.html
+++ b/microsoft_cfb/javascript.html
@@ -603,7 +603,7 @@ <h3>MicrosoftCfb.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/lua.html b/microsoft_cfb/lua.html
index c838d9946..09d070f47 100644
--- a/microsoft_cfb/lua.html
+++ b/microsoft_cfb/lua.html
@@ -529,7 +529,7 @@ <h3>microsoft_cfb.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/nim.html b/microsoft_cfb/nim.html
index 4ca8d58f0..b459b72be 100644
--- a/microsoft_cfb/nim.html
+++ b/microsoft_cfb/nim.html
@@ -623,7 +623,7 @@ <h3>microsoft_cfb.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/perl.html b/microsoft_cfb/perl.html
index a1b26f146..d168562f4 100644
--- a/microsoft_cfb/perl.html
+++ b/microsoft_cfb/perl.html
@@ -705,7 +705,7 @@ <h3>MicrosoftCfb.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/php.html b/microsoft_cfb/php.html
index 32e1ff3f0..d0a4f73b9 100644
--- a/microsoft_cfb/php.html
+++ b/microsoft_cfb/php.html
@@ -604,7 +604,7 @@ <h3>MicrosoftCfb.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/python.html b/microsoft_cfb/python.html
index 2be4659e9..f9409e731 100644
--- a/microsoft_cfb/python.html
+++ b/microsoft_cfb/python.html
@@ -507,7 +507,7 @@ <h3>microsoft_cfb.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_cfb/ruby.html b/microsoft_cfb/ruby.html
index bf52f0549..f12403cf0 100644
--- a/microsoft_cfb/ruby.html
+++ b/microsoft_cfb/ruby.html
@@ -570,7 +570,7 @@ <h3>microsoft_cfb.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/cpp_stl_11.html b/microsoft_network_monitor_v2/cpp_stl_11.html
index e6e0733f2..b605c2574 100644
--- a/microsoft_network_monitor_v2/cpp_stl_11.html
+++ b/microsoft_network_monitor_v2/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -899,7 +899,7 @@ <h3>microsoft_network_monitor_v2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/cpp_stl_98.html b/microsoft_network_monitor_v2/cpp_stl_98.html
index e242b37e8..510610c54 100644
--- a/microsoft_network_monitor_v2/cpp_stl_98.html
+++ b/microsoft_network_monitor_v2/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -949,7 +949,7 @@ <h3>microsoft_network_monitor_v2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/csharp.html b/microsoft_network_monitor_v2/csharp.html
index ede03f80c..83319942a 100644
--- a/microsoft_network_monitor_v2/csharp.html
+++ b/microsoft_network_monitor_v2/csharp.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -740,7 +740,7 @@ <h3>MicrosoftNetworkMonitorV2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/go.html b/microsoft_network_monitor_v2/go.html
index 20d9a8063..e4108b767 100644
--- a/microsoft_network_monitor_v2/go.html
+++ b/microsoft_network_monitor_v2/go.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -783,7 +783,7 @@ <h3>microsoft_network_monitor_v2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/graphviz.html b/microsoft_network_monitor_v2/graphviz.html
index 302dc8cb8..095836519 100644
--- a/microsoft_network_monitor_v2/graphviz.html
+++ b/microsoft_network_monitor_v2/graphviz.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -376,7 +376,7 @@ <h3>microsoft_network_monitor_v2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/index.html b/microsoft_network_monitor_v2/index.html
index a709d012a..2b81a0dc6 100644
--- a/microsoft_network_monitor_v2/index.html
+++ b/microsoft_network_monitor_v2/index.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -502,7 +502,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/java.html b/microsoft_network_monitor_v2/java.html
index 5dfa945ef..065e70a59 100644
--- a/microsoft_network_monitor_v2/java.html
+++ b/microsoft_network_monitor_v2/java.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -763,7 +763,7 @@ <h3>MicrosoftNetworkMonitorV2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/javascript.html b/microsoft_network_monitor_v2/javascript.html
index eaece1415..581ad1fbe 100644
--- a/microsoft_network_monitor_v2/javascript.html
+++ b/microsoft_network_monitor_v2/javascript.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -747,7 +747,7 @@ <h3>MicrosoftNetworkMonitorV2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/lua.html b/microsoft_network_monitor_v2/lua.html
index 7ee1270de..18ada654b 100644
--- a/microsoft_network_monitor_v2/lua.html
+++ b/microsoft_network_monitor_v2/lua.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -570,7 +570,7 @@ <h3>microsoft_network_monitor_v2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/nim.html b/microsoft_network_monitor_v2/nim.html
index a9b104594..199aaf8ae 100644
--- a/microsoft_network_monitor_v2/nim.html
+++ b/microsoft_network_monitor_v2/nim.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -656,7 +656,7 @@ <h3>microsoft_network_monitor_v2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/perl.html b/microsoft_network_monitor_v2/perl.html
index df1d5e925..acd574364 100644
--- a/microsoft_network_monitor_v2/perl.html
+++ b/microsoft_network_monitor_v2/perl.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -718,7 +718,7 @@ <h3>MicrosoftNetworkMonitorV2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/php.html b/microsoft_network_monitor_v2/php.html
index 31ed856b1..c21fdd29b 100644
--- a/microsoft_network_monitor_v2/php.html
+++ b/microsoft_network_monitor_v2/php.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -632,7 +632,7 @@ <h3>MicrosoftNetworkMonitorV2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/python.html b/microsoft_network_monitor_v2/python.html
index 2660ad5ef..d826430ad 100644
--- a/microsoft_network_monitor_v2/python.html
+++ b/microsoft_network_monitor_v2/python.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -580,7 +580,7 @@ <h3>microsoft_network_monitor_v2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_network_monitor_v2/ruby.html b/microsoft_network_monitor_v2/ruby.html
index 616be682a..414938020 100644
--- a/microsoft_network_monitor_v2/ruby.html
+++ b/microsoft_network_monitor_v2/ruby.html
@@ -105,12 +105,12 @@ <h1>.cap file format of Microsoft Network Monitor, v2.x:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's
-network packet sniffing and analysis tool. It can save captured
-traffic as .cap files, which usually contain the packets and may
-contain some additional info - enhanced network info, calculated
+                <p><p>Microsoft Network Monitor (AKA Netmon) is a proprietary Microsoft's<br />
+network packet sniffing and analysis tool. It can save captured<br />
+traffic as .cap files, which usually contain the packets and may<br />
+contain some additional info - enhanced network info, calculated<br />
 statistics, etc.</p>
-<p>There are at least 2 different versions of the format: v1 and
+<p>There are at least 2 different versions of the format: v1 and<br />
 v2. Netmon v3 seems to use the same file format as v1.</p>
 </p>
             </div>
@@ -627,7 +627,7 @@ <h3>microsoft_network_monitor_v2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/cpp_stl_11.html b/microsoft_pe/cpp_stl_11.html
index 5295a25e9..5267b80a9 100644
--- a/microsoft_pe/cpp_stl_11.html
+++ b/microsoft_pe/cpp_stl_11.html
@@ -1825,7 +1825,7 @@ <h3>microsoft_pe.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/cpp_stl_98.html b/microsoft_pe/cpp_stl_98.html
index b7cceda5d..8e766c9fd 100644
--- a/microsoft_pe/cpp_stl_98.html
+++ b/microsoft_pe/cpp_stl_98.html
@@ -2010,7 +2010,7 @@ <h3>microsoft_pe.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/csharp.html b/microsoft_pe/csharp.html
index c7a29ea99..b45ee36cb 100644
--- a/microsoft_pe/csharp.html
+++ b/microsoft_pe/csharp.html
@@ -1295,7 +1295,7 @@ <h3>MicrosoftPe.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/go.html b/microsoft_pe/go.html
index ab6c4f5e3..83beae323 100644
--- a/microsoft_pe/go.html
+++ b/microsoft_pe/go.html
@@ -1659,7 +1659,7 @@ <h3>microsoft_pe.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/graphviz.html b/microsoft_pe/graphviz.html
index ad0e3ffd0..16153efaa 100644
--- a/microsoft_pe/graphviz.html
+++ b/microsoft_pe/graphviz.html
@@ -604,7 +604,7 @@ <h3>microsoft_pe.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/index.html b/microsoft_pe/index.html
index 261017d70..19c289320 100644
--- a/microsoft_pe/index.html
+++ b/microsoft_pe/index.html
@@ -759,7 +759,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/java.html b/microsoft_pe/java.html
index 1b8ffded0..cdcd38eaf 100644
--- a/microsoft_pe/java.html
+++ b/microsoft_pe/java.html
@@ -1317,7 +1317,7 @@ <h3>MicrosoftPe.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/javascript.html b/microsoft_pe/javascript.html
index c024d59a8..78286a5bb 100644
--- a/microsoft_pe/javascript.html
+++ b/microsoft_pe/javascript.html
@@ -971,7 +971,7 @@ <h3>MicrosoftPe.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/lua.html b/microsoft_pe/lua.html
index 23498e8ce..0e6c78906 100644
--- a/microsoft_pe/lua.html
+++ b/microsoft_pe/lua.html
@@ -872,7 +872,7 @@ <h3>microsoft_pe.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/nim.html b/microsoft_pe/nim.html
index 66092b086..a4acae8b2 100644
--- a/microsoft_pe/nim.html
+++ b/microsoft_pe/nim.html
@@ -1080,7 +1080,7 @@ <h3>microsoft_pe.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/perl.html b/microsoft_pe/perl.html
index 9dcc71dce..6bd6e3a2f 100644
--- a/microsoft_pe/perl.html
+++ b/microsoft_pe/perl.html
@@ -1533,7 +1533,7 @@ <h3>MicrosoftPe.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/php.html b/microsoft_pe/php.html
index ff6502f4d..b45a0f574 100644
--- a/microsoft_pe/php.html
+++ b/microsoft_pe/php.html
@@ -1158,7 +1158,7 @@ <h3>MicrosoftPe.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/python.html b/microsoft_pe/python.html
index 388695ffe..6cfeecec6 100644
--- a/microsoft_pe/python.html
+++ b/microsoft_pe/python.html
@@ -835,7 +835,7 @@ <h3>microsoft_pe.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/microsoft_pe/ruby.html b/microsoft_pe/ruby.html
index ea67d2a02..47a7844ab 100644
--- a/microsoft_pe/ruby.html
+++ b/microsoft_pe/ruby.html
@@ -904,7 +904,7 @@ <h3>microsoft_pe.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/cpp_stl_11.html b/mifare_classic/cpp_stl_11.html
index 981a3a3a0..dc10c2233 100644
--- a/mifare_classic/cpp_stl_11.html
+++ b/mifare_classic/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1840,7 +1840,7 @@ <h3>mifare_classic.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/cpp_stl_98.html b/mifare_classic/cpp_stl_98.html
index 47abcd432..778b37838 100644
--- a/mifare_classic/cpp_stl_98.html
+++ b/mifare_classic/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -2025,7 +2025,7 @@ <h3>mifare_classic.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/csharp.html b/mifare_classic/csharp.html
index 7be5542f7..8219e902a 100644
--- a/mifare_classic/csharp.html
+++ b/mifare_classic/csharp.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1332,7 +1332,7 @@ <h3>MifareClassic.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/go.html b/mifare_classic/go.html
index 7d459615d..59633a00e 100644
--- a/mifare_classic/go.html
+++ b/mifare_classic/go.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1600,7 +1600,7 @@ <h3>mifare_classic.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/graphviz.html b/mifare_classic/graphviz.html
index bc05aff2e..be104367c 100644
--- a/mifare_classic/graphviz.html
+++ b/mifare_classic/graphviz.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -657,7 +657,7 @@ <h3>mifare_classic.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/index.html b/mifare_classic/index.html
index e709fe968..9f352dae6 100644
--- a/mifare_classic/index.html
+++ b/mifare_classic/index.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -520,7 +520,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/java.html b/mifare_classic/java.html
index d6bd4f0aa..af0d9a1cb 100644
--- a/mifare_classic/java.html
+++ b/mifare_classic/java.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1189,7 +1189,7 @@ <h3>MifareClassic.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/javascript.html b/mifare_classic/javascript.html
index e97025245..a3fbe610c 100644
--- a/mifare_classic/javascript.html
+++ b/mifare_classic/javascript.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -970,7 +970,7 @@ <h3>MifareClassic.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/lua.html b/mifare_classic/lua.html
index bbca86453..0d9f5934c 100644
--- a/mifare_classic/lua.html
+++ b/mifare_classic/lua.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -970,7 +970,7 @@ <h3>mifare_classic.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/nim.html b/mifare_classic/nim.html
index 3006c2f41..eddd0b021 100644
--- a/mifare_classic/nim.html
+++ b/mifare_classic/nim.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1084,7 +1084,7 @@ <h3>mifare_classic.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/perl.html b/mifare_classic/perl.html
index 1e5773d2f..b4f40539b 100644
--- a/mifare_classic/perl.html
+++ b/mifare_classic/perl.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -1276,7 +1276,7 @@ <h3>MifareClassic.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/php.html b/mifare_classic/php.html
index 3055a53a6..e89592d97 100644
--- a/mifare_classic/php.html
+++ b/mifare_classic/php.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -922,7 +922,7 @@ <h3>MifareClassic.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/python.html b/mifare_classic/python.html
index 4b39da407..99c6e144d 100644
--- a/mifare_classic/python.html
+++ b/mifare_classic/python.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -893,7 +893,7 @@ <h3>mifare_classic.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mifare_classic/ruby.html b/mifare_classic/ruby.html
index 4e46c1366..fe6fd5bb6 100644
--- a/mifare_classic/ruby.html
+++ b/mifare_classic/ruby.html
@@ -105,7 +105,7 @@ <h1>Mifare Classic RFID tag dump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>You can get a dump for testing from this link:
+                <p><p>You can get a dump for testing from this link:<br />
 <a href="https://github.com/zhovner/mfdread/raw/master/dump.mfd">https://github.com/zhovner/mfdread/raw/master/dump.mfd</a></p>
 </p>
             </div>
@@ -825,7 +825,7 @@ <h3>mifare_classic.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/csharp.html b/minecraft_nbt/csharp.html
index 4da61f62f..9a210f599 100644
--- a/minecraft_nbt/csharp.html
+++ b/minecraft_nbt/csharp.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -902,7 +902,7 @@ <h3>MinecraftNbt.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/go.html b/minecraft_nbt/go.html
index 0cc5ca153..c4fd4c348 100644
--- a/minecraft_nbt/go.html
+++ b/minecraft_nbt/go.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -953,7 +953,7 @@ <h3>minecraft_nbt.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/graphviz.html b/minecraft_nbt/graphviz.html
index 8c9a6ebf2..e3efd943e 100644
--- a/minecraft_nbt/graphviz.html
+++ b/minecraft_nbt/graphviz.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -487,7 +487,7 @@ <h3>minecraft_nbt.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/index.html b/minecraft_nbt/index.html
index 15948efa0..3c2e0edee 100644
--- a/minecraft_nbt/index.html
+++ b/minecraft_nbt/index.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -548,7 +548,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/java.html b/minecraft_nbt/java.html
index af90c861c..57c6e1401 100644
--- a/minecraft_nbt/java.html
+++ b/minecraft_nbt/java.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -924,7 +924,7 @@ <h3>MinecraftNbt.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/javascript.html b/minecraft_nbt/javascript.html
index 9ab6b0356..7edc43fb0 100644
--- a/minecraft_nbt/javascript.html
+++ b/minecraft_nbt/javascript.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -760,7 +760,7 @@ <h3>MinecraftNbt.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/lua.html b/minecraft_nbt/lua.html
index e1e2f7dbc..d297ee52f 100644
--- a/minecraft_nbt/lua.html
+++ b/minecraft_nbt/lua.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -680,7 +680,7 @@ <h3>minecraft_nbt.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/nim.html b/minecraft_nbt/nim.html
index 768eec27d..a4aed3d36 100644
--- a/minecraft_nbt/nim.html
+++ b/minecraft_nbt/nim.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -743,7 +743,7 @@ <h3>minecraft_nbt.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/perl.html b/minecraft_nbt/perl.html
index 8146fd690..5dd968190 100644
--- a/minecraft_nbt/perl.html
+++ b/minecraft_nbt/perl.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -843,7 +843,7 @@ <h3>MinecraftNbt.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/php.html b/minecraft_nbt/php.html
index aeab1b12e..ff89c57c2 100644
--- a/minecraft_nbt/php.html
+++ b/minecraft_nbt/php.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -718,7 +718,7 @@ <h3>MinecraftNbt.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/python.html b/minecraft_nbt/python.html
index 12fe07a19..17e7e2ddd 100644
--- a/minecraft_nbt/python.html
+++ b/minecraft_nbt/python.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -690,7 +690,7 @@ <h3>minecraft_nbt.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/minecraft_nbt/ruby.html b/minecraft_nbt/ruby.html
index dc733b21d..25df59217 100644
--- a/minecraft_nbt/ruby.html
+++ b/minecraft_nbt/ruby.html
@@ -105,22 +105,22 @@ <h1>Minecraft NBT (Named Binary Tag):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A structured binary format native to Minecraft for saving game data and transferring
-it over the network (in multiplayer), such as player data
-(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains
-e.g. player's inventory and location), saved worlds
-(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),
-list of saved multiplayer servers
-(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -
+                <p><p>A structured binary format native to Minecraft for saving game data and transferring<br />
+it over the network (in multiplayer), such as player data<br />
+(<a href="https://minecraft.wiki/w/Player.dat_format"><code>&lt;player&gt;.dat</code></a>; contains<br />
+e.g. player's inventory and location), saved worlds<br />
+(<a href="https://minecraft.wiki/w/Java_Edition_level_format#level.dat_format"><code>level.dat</code></a> and <a href="https://minecraft.wiki/w/Chunk_format#NBT_structure">Chunk format</a>),<br />
+list of saved multiplayer servers<br />
+(<a href="https://minecraft.wiki/w/Servers.dat_format"><code>servers.dat</code></a>) and so on -<br />
 see <a href="https://minecraft.wiki/w/NBT_format#Uses">https://minecraft.wiki/w/NBT_format#Uses</a>.</p>
-<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original
+<p>The entire file should be <em>gzip</em>-compressed (in accordance with the original<br />
 specification <a href="https://web.archive.org/web/20110723210920/https://www.minecraft.net/docs/NBT.txt">NBT.txt</a> by Notch), but can also be compressed with <em>zlib</em> or uncompressed.</p>
-<p>This spec can only handle uncompressed NBT data, so be sure to first detect
-what type of data you are dealing with. You can use the Unix <code>file</code> command
-to do this (<code>file-5.20</code> or later is required; older versions do not recognize
+<p>This spec can only handle uncompressed NBT data, so be sure to first detect<br />
+what type of data you are dealing with. You can use the Unix <code>file</code> command<br />
+to do this (<code>file-5.20</code> or later is required; older versions do not recognize<br />
 <em>zlib</em>-compressed data and return <code>application/octet-stream</code> instead):</p>
-<pre><code class="language-shell">file --brief --mime-type input-unknown.nbt
-</code></pre>
+<pre lang="shell" style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">file --brief --mime-type input-unknown.nbt
+</span></code></pre>
 <p>If it says:</p>
 <ul>
 <li><code>application/x-gzip</code> or <code>application/gzip</code> (since <code>file-5.37</code>), you can decompress it by
@@ -135,26 +135,26 @@ <h1>Minecraft NBT (Named Binary Tag):
 <li><code>python3 -c &quot;import sys, zlib; sys.stdout.buffer.write( zlib.decompress(sys.stdin.buffer.read()) )&quot; &lt; input-zlib.nbt &gt; output.nbt</code></li>
 </ul>
 </li>
-<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),
+<li>something else (especially <code>image/x-pcx</code> and <code>application/octet-stream</code>),<br />
 it is most likely already uncompressed.</li>
 </ul>
-<p>The file <code>output.nbt</code> generated by one of the above commands can already be
+<p>The file <code>output.nbt</code> generated by one of the above commands can already be<br />
 processed with this Kaitai Struct specification.</p>
-<p>This spec <strong>only</strong> implements the Java edition format. There is also
-a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,
-which uses little-endian encoding and has a few other differences, but it isn't
+<p>This spec <strong>only</strong> implements the Java edition format. There is also<br />
+a <a href="https://wiki.vg/NBT#Bedrock_edition">Bedrock edition</a> NBT format,<br />
+which uses little-endian encoding and has a few other differences, but it isn't<br />
 as popular as the Java edition format.</p>
-<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with
-standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target
-languages, and thus one must use external libraries to achieve a fully-compliant
-decoder. But decoding in standard UTF-8 is still better than nothing, and
+<p><strong>Implementation note:</strong> strings in <code>TAG_String</code> are incorrectly decoded with<br />
+standard UTF-8, while they are encoded in <a href="https://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8"><strong>Modified UTF-8</strong></a> (MUTF-8). That's because MUTF-8 is not supported natively by most target<br />
+languages, and thus one must use external libraries to achieve a fully-compliant<br />
+decoder. But decoding in standard UTF-8 is still better than nothing, and<br />
 it usually works fine.</p>
-<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are
-U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF
-(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).
-A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully
-decoded as UTF-8. The behavior in this case depends on the target language -
-usually an exception is thrown, or the bytes that are not valid UTF-8
+<p>All Unicode code points with incompatible representations in MUTF-8 and UTF-8 are<br />
+U+0000 (<em>NUL</em>), U+D800-U+DFFF (<em>High</em> and <em>Low Surrogates</em>) and U+10000-U+10FFFF<br />
+(all <em>Supplementary</em> Planes; includes e.g. emoticons, pictograms).<br />
+A <em>MUTF-8</em>-encoded string containing these code points cannot be successfully<br />
+decoded as UTF-8. The behavior in this case depends on the target language -<br />
+usually an exception is thrown, or the bytes that are not valid UTF-8<br />
 are replaced or ignored.</p>
 <p><strong>Sample files:</strong></p>
 <ul>
@@ -688,7 +688,7 @@ <h3>minecraft_nbt.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/cpp_stl_11.html b/monomakh_sapr_chg/cpp_stl_11.html
index 594e73601..163e3c319 100644
--- a/monomakh_sapr_chg/cpp_stl_11.html
+++ b/monomakh_sapr_chg/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -492,7 +492,7 @@ <h3>monomakh_sapr_chg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/cpp_stl_98.html b/monomakh_sapr_chg/cpp_stl_98.html
index 798f0d249..5a6761c2b 100644
--- a/monomakh_sapr_chg/cpp_stl_98.html
+++ b/monomakh_sapr_chg/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -512,7 +512,7 @@ <h3>monomakh_sapr_chg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/csharp.html b/monomakh_sapr_chg/csharp.html
index ca8b3fdb9..fe106340d 100644
--- a/monomakh_sapr_chg/csharp.html
+++ b/monomakh_sapr_chg/csharp.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -395,7 +395,7 @@ <h3>MonomakhSaprChg.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/go.html b/monomakh_sapr_chg/go.html
index e5911cb86..d42b7a462 100644
--- a/monomakh_sapr_chg/go.html
+++ b/monomakh_sapr_chg/go.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -363,7 +363,7 @@ <h3>monomakh_sapr_chg.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/graphviz.html b/monomakh_sapr_chg/graphviz.html
index f69253327..bfa0792e7 100644
--- a/monomakh_sapr_chg/graphviz.html
+++ b/monomakh_sapr_chg/graphviz.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -298,7 +298,7 @@ <h3>monomakh_sapr_chg.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/index.html b/monomakh_sapr_chg/index.html
index 7565d95de..36b49fcc7 100644
--- a/monomakh_sapr_chg/index.html
+++ b/monomakh_sapr_chg/index.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -293,7 +293,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/java.html b/monomakh_sapr_chg/java.html
index 18e195e8d..f3c89952c 100644
--- a/monomakh_sapr_chg/java.html
+++ b/monomakh_sapr_chg/java.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -409,7 +409,7 @@ <h3>MonomakhSaprChg.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/javascript.html b/monomakh_sapr_chg/javascript.html
index dd9af4397..e4210f90d 100644
--- a/monomakh_sapr_chg/javascript.html
+++ b/monomakh_sapr_chg/javascript.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -371,7 +371,7 @@ <h3>MonomakhSaprChg.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/lua.html b/monomakh_sapr_chg/lua.html
index bff734002..721d8af8b 100644
--- a/monomakh_sapr_chg/lua.html
+++ b/monomakh_sapr_chg/lua.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -322,7 +322,7 @@ <h3>monomakh_sapr_chg.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/nim.html b/monomakh_sapr_chg/nim.html
index 27deead10..668e68115 100644
--- a/monomakh_sapr_chg/nim.html
+++ b/monomakh_sapr_chg/nim.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -338,7 +338,7 @@ <h3>monomakh_sapr_chg.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/perl.html b/monomakh_sapr_chg/perl.html
index 45cbce830..c566bb83e 100644
--- a/monomakh_sapr_chg/perl.html
+++ b/monomakh_sapr_chg/perl.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -375,7 +375,7 @@ <h3>MonomakhSaprChg.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/php.html b/monomakh_sapr_chg/php.html
index 1930d5361..c5bb97cd3 100644
--- a/monomakh_sapr_chg/php.html
+++ b/monomakh_sapr_chg/php.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -328,7 +328,7 @@ <h3>MonomakhSaprChg.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/python.html b/monomakh_sapr_chg/python.html
index de44a1af4..9f748917d 100644
--- a/monomakh_sapr_chg/python.html
+++ b/monomakh_sapr_chg/python.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -360,7 +360,7 @@ <h3>monomakh_sapr_chg.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/monomakh_sapr_chg/ruby.html b/monomakh_sapr_chg/ruby.html
index 8215d13ea..9b5098be2 100644
--- a/monomakh_sapr_chg/ruby.html
+++ b/monomakh_sapr_chg/ruby.html
@@ -105,11 +105,11 @@ <h1>.chg file format of MONOMAKH-SAPR:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>CHG is a container format file used by
-<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software
-package for analysis &amp; design of reinforced concrete multi-storey
+                <p><p>CHG is a container format file used by<br />
+<a href="https://www.liraland.com/mono/">MONOMAKH-SAPR</a>, a software<br />
+package for analysis &amp; design of reinforced concrete multi-storey<br />
 buildings with arbitrary configuration in plan.</p>
-<p>CHG is a simple container, which bundles several project files
+<p>CHG is a simple container, which bundles several project files<br />
 together.</p>
 <p>Written and tested by Vladimir Shulzhitskiy, 2017</p>
 </p>
@@ -366,7 +366,7 @@ <h3>monomakh_sapr_chg.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/cpp_stl_11.html b/mozilla_mar/cpp_stl_11.html
index 4ae387ef0..e7cea7915 100644
--- a/mozilla_mar/cpp_stl_11.html
+++ b/mozilla_mar/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -848,7 +848,7 @@ <h3>mozilla_mar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/cpp_stl_98.html b/mozilla_mar/cpp_stl_98.html
index 6f922d820..2c7dad11d 100644
--- a/mozilla_mar/cpp_stl_98.html
+++ b/mozilla_mar/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -925,7 +925,7 @@ <h3>mozilla_mar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/csharp.html b/mozilla_mar/csharp.html
index eea60b00b..ee7f18ca1 100644
--- a/mozilla_mar/csharp.html
+++ b/mozilla_mar/csharp.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -637,7 +637,7 @@ <h3>MozillaMar.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/go.html b/mozilla_mar/go.html
index 3f8a464e9..8fda35f9b 100644
--- a/mozilla_mar/go.html
+++ b/mozilla_mar/go.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -671,7 +671,7 @@ <h3>mozilla_mar.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/graphviz.html b/mozilla_mar/graphviz.html
index b935e9162..aef638f90 100644
--- a/mozilla_mar/graphviz.html
+++ b/mozilla_mar/graphviz.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -391,7 +391,7 @@ <h3>mozilla_mar.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/index.html b/mozilla_mar/index.html
index 834f02adc..140a9ef53 100644
--- a/mozilla_mar/index.html
+++ b/mozilla_mar/index.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -385,7 +385,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/java.html b/mozilla_mar/java.html
index 4fadda97e..b9353f2bd 100644
--- a/mozilla_mar/java.html
+++ b/mozilla_mar/java.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -685,7 +685,7 @@ <h3>MozillaMar.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/javascript.html b/mozilla_mar/javascript.html
index d3e5d5011..b66e15ee0 100644
--- a/mozilla_mar/javascript.html
+++ b/mozilla_mar/javascript.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -524,7 +524,7 @@ <h3>MozillaMar.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/lua.html b/mozilla_mar/lua.html
index dc8248368..55d3f2622 100644
--- a/mozilla_mar/lua.html
+++ b/mozilla_mar/lua.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -467,7 +467,7 @@ <h3>mozilla_mar.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/nim.html b/mozilla_mar/nim.html
index 4f23b6a3e..092d49f2d 100644
--- a/mozilla_mar/nim.html
+++ b/mozilla_mar/nim.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -523,7 +523,7 @@ <h3>mozilla_mar.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/perl.html b/mozilla_mar/perl.html
index 8e0b849dc..cccc041f3 100644
--- a/mozilla_mar/perl.html
+++ b/mozilla_mar/perl.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -700,7 +700,7 @@ <h3>MozillaMar.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/php.html b/mozilla_mar/php.html
index 57a9d2ab3..24016d7c5 100644
--- a/mozilla_mar/php.html
+++ b/mozilla_mar/php.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -507,7 +507,7 @@ <h3>MozillaMar.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/python.html b/mozilla_mar/python.html
index 6f358a8a5..463438c2c 100644
--- a/mozilla_mar/python.html
+++ b/mozilla_mar/python.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -482,7 +482,7 @@ <h3>mozilla_mar.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/mozilla_mar/ruby.html b/mozilla_mar/ruby.html
index 752f6f059..b6db18c1b 100644
--- a/mozilla_mar/ruby.html
+++ b/mozilla_mar/ruby.html
@@ -105,7 +105,7 @@ <h1>Mozilla ARchive:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.
+                <p><p>Mozilla ARchive file is Mozilla's own archive format to distribute software updates.<br />
 Test files can be found on Mozilla's FTP site, for example:</p>
 <p><a href="http://ftp.mozilla.org/pub/firefox/nightly/partials/">http://ftp.mozilla.org/pub/firefox/nightly/partials/</a></p>
 </p>
@@ -504,7 +504,7 @@ <h3>mozilla_mar.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/cpp_stl_11.html b/msgpack/cpp_stl_11.html
index 45b8cd5f6..8dbf5c451 100644
--- a/msgpack/cpp_stl_11.html
+++ b/msgpack/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -1342,7 +1342,7 @@ <h3>msgpack.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/cpp_stl_98.html b/msgpack/cpp_stl_98.html
index f7db4e502..973a0dc98 100644
--- a/msgpack/cpp_stl_98.html
+++ b/msgpack/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -1374,7 +1374,7 @@ <h3>msgpack.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/csharp.html b/msgpack/csharp.html
index 968f9abfc..f955addab 100644
--- a/msgpack/csharp.html
+++ b/msgpack/csharp.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -985,7 +985,7 @@ <h3>Msgpack.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/go.html b/msgpack/go.html
index e3796c8f6..bfdc31c16 100644
--- a/msgpack/go.html
+++ b/msgpack/go.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -1131,7 +1131,7 @@ <h3>msgpack.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/graphviz.html b/msgpack/graphviz.html
index 723c1fa2b..9f6c8b52f 100644
--- a/msgpack/graphviz.html
+++ b/msgpack/graphviz.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -495,7 +495,7 @@ <h3>msgpack.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/index.html b/msgpack/index.html
index 682a562d9..0662d13a4 100644
--- a/msgpack/index.html
+++ b/msgpack/index.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -453,7 +453,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/java.html b/msgpack/java.html
index e1873a1b3..96936e8b6 100644
--- a/msgpack/java.html
+++ b/msgpack/java.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -821,7 +821,7 @@ <h3>Msgpack.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/javascript.html b/msgpack/javascript.html
index a7bba4cb7..99fd8b95a 100644
--- a/msgpack/javascript.html
+++ b/msgpack/javascript.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -755,7 +755,7 @@ <h3>Msgpack.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/lua.html b/msgpack/lua.html
index 594f64084..aaafc93ce 100644
--- a/msgpack/lua.html
+++ b/msgpack/lua.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>msgpack.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/nim.html b/msgpack/nim.html
index a61e801fa..8608fa0f5 100644
--- a/msgpack/nim.html
+++ b/msgpack/nim.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -806,7 +806,7 @@ <h3>msgpack.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/perl.html b/msgpack/perl.html
index f4c93fb59..7e081c343 100644
--- a/msgpack/perl.html
+++ b/msgpack/perl.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -714,7 +714,7 @@ <h3>Msgpack.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/php.html b/msgpack/php.html
index 695629591..a80b8dece 100644
--- a/msgpack/php.html
+++ b/msgpack/php.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -632,7 +632,7 @@ <h3>Msgpack.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/python.html b/msgpack/python.html
index 9bef08b0d..f731965c0 100644
--- a/msgpack/python.html
+++ b/msgpack/python.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -732,7 +732,7 @@ <h3>msgpack.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/msgpack/ruby.html b/msgpack/ruby.html
index 363b01a1e..990bc7cc9 100644
--- a/msgpack/ruby.html
+++ b/msgpack/ruby.html
@@ -105,7 +105,7 @@ <h1>MessagePack (msgpack) serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured
+                <p><p>MessagePack (msgpack) is a system to serialize arbitrary structured<br />
 data into a compact binary stream.</p>
 </p>
             </div>
@@ -647,7 +647,7 @@ <h3>msgpack.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/cpp_stl_11.html b/nitf/cpp_stl_11.html
index eab8bbf8e..699d3bf16 100644
--- a/nitf/cpp_stl_11.html
+++ b/nitf/cpp_stl_11.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -2654,7 +2654,7 @@ <h3>nitf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/cpp_stl_98.html b/nitf/cpp_stl_98.html
index ffd3a9fe0..d89f65a82 100644
--- a/nitf/cpp_stl_98.html
+++ b/nitf/cpp_stl_98.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -2998,7 +2998,7 @@ <h3>nitf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/csharp.html b/nitf/csharp.html
index 3b1e11477..d714ef0ee 100644
--- a/nitf/csharp.html
+++ b/nitf/csharp.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1868,7 +1868,7 @@ <h3>Nitf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/go.html b/nitf/go.html
index 1f7f1a9c4..15af452c8 100644
--- a/nitf/go.html
+++ b/nitf/go.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -2678,7 +2678,7 @@ <h3>nitf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/graphviz.html b/nitf/graphviz.html
index 5751dde43..e9c279d42 100644
--- a/nitf/graphviz.html
+++ b/nitf/graphviz.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -849,7 +849,7 @@ <h3>nitf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/index.html b/nitf/index.html
index cdefd020a..65da3f652 100644
--- a/nitf/index.html
+++ b/nitf/index.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1100,7 +1100,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/java.html b/nitf/java.html
index c8b4b8494..e20a4fd3d 100644
--- a/nitf/java.html
+++ b/nitf/java.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1939,7 +1939,7 @@ <h3>Nitf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/javascript.html b/nitf/javascript.html
index 465f30a15..856596a92 100644
--- a/nitf/javascript.html
+++ b/nitf/javascript.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1233,7 +1233,7 @@ <h3>Nitf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/lua.html b/nitf/lua.html
index 78dced519..d7628d109 100644
--- a/nitf/lua.html
+++ b/nitf/lua.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1122,7 +1122,7 @@ <h3>nitf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/nim.html b/nitf/nim.html
index 4d1e6e067..7208c38ec 100644
--- a/nitf/nim.html
+++ b/nitf/nim.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1549,7 +1549,7 @@ <h3>nitf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/perl.html b/nitf/perl.html
index 0797cb13a..fd287737e 100644
--- a/nitf/perl.html
+++ b/nitf/perl.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -2500,7 +2500,7 @@ <h3>Nitf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/php.html b/nitf/php.html
index 29eab4956..15bc06c69 100644
--- a/nitf/php.html
+++ b/nitf/php.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1518,7 +1518,7 @@ <h3>Nitf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/python.html b/nitf/python.html
index 5771dde76..6f38a86b5 100644
--- a/nitf/python.html
+++ b/nitf/python.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1000,7 +1000,7 @@ <h3>nitf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nitf/ruby.html b/nitf/ruby.html
index 560150acb..9cbaad2f4 100644
--- a/nitf/ruby.html
+++ b/nitf/ruby.html
@@ -105,15 +105,15 @@ <h1>National Imagery Transmission Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for
+                <p><p>The NITF (National Image Transition Format) format is a file format developed by the U.S. Government for<br />
 storing imagery, e.g. from satellites.</p>
 <p>According to the <a href="https://web.archive.org/web/20181105050336/https://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf">foreword of the specification</a>:</p>
 <blockquote>
-<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital
-imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as
+<p>The National Imagery Transmission Format Standard (NITFS) is the suite of standards for formatting digital<br />
+imagery and imagery-related products and exchanging them among members of the Intelligence Community (IC) as<br />
 defined by the Executive Order 12333, and other United States Government departments and agencies.&quot;</p>
 </blockquote>
-<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.
+<p>This implementation is set to version format (<code>file_version</code>) of 02.10 and <code>standard_type</code> of <code>BF01</code>.<br />
 It was implemented by <a href="https://www.riverloopsecurity.com/">River Loop Security</a>.</p>
 </p>
             </div>
@@ -1237,7 +1237,7 @@ <h3>nitf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/cpp_stl_11.html b/nt_mdt/cpp_stl_11.html
index bcfadc667..6873ddd33 100644
--- a/nt_mdt/cpp_stl_11.html
+++ b/nt_mdt/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -2751,7 +2751,7 @@ <h3>nt_mdt.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/cpp_stl_98.html b/nt_mdt/cpp_stl_98.html
index 659e175e8..1f8c21f3e 100644
--- a/nt_mdt/cpp_stl_98.html
+++ b/nt_mdt/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -3095,7 +3095,7 @@ <h3>nt_mdt.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/csharp.html b/nt_mdt/csharp.html
index 8fdd984e4..46257b6ed 100644
--- a/nt_mdt/csharp.html
+++ b/nt_mdt/csharp.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -2037,7 +2037,7 @@ <h3>NtMdt.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/graphviz.html b/nt_mdt/graphviz.html
index 7fe8098ae..d14d660c7 100644
--- a/nt_mdt/graphviz.html
+++ b/nt_mdt/graphviz.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -774,7 +774,7 @@ <h3>nt_mdt.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/index.html b/nt_mdt/index.html
index 29c486274..403c6026f 100644
--- a/nt_mdt/index.html
+++ b/nt_mdt/index.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1037,7 +1037,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/java.html b/nt_mdt/java.html
index a1a56802a..88ca68833 100644
--- a/nt_mdt/java.html
+++ b/nt_mdt/java.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -2280,7 +2280,7 @@ <h3>NtMdt.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/javascript.html b/nt_mdt/javascript.html
index a328e43fd..578a8d926 100644
--- a/nt_mdt/javascript.html
+++ b/nt_mdt/javascript.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1594,7 +1594,7 @@ <h3>NtMdt.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/nim.html b/nt_mdt/nim.html
index f29d1d042..2ecfd5cd0 100644
--- a/nt_mdt/nim.html
+++ b/nt_mdt/nim.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1711,7 +1711,7 @@ <h3>nt_mdt.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/perl.html b/nt_mdt/perl.html
index f2b0aea56..9e4ff3216 100644
--- a/nt_mdt/perl.html
+++ b/nt_mdt/perl.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -2564,7 +2564,7 @@ <h3>NtMdt.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/php.html b/nt_mdt/php.html
index 03afec5dc..ce6bbdecd 100644
--- a/nt_mdt/php.html
+++ b/nt_mdt/php.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1710,7 +1710,7 @@ <h3>NtMdt.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/python.html b/nt_mdt/python.html
index af984de76..bdcd5802f 100644
--- a/nt_mdt/python.html
+++ b/nt_mdt/python.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1097,7 +1097,7 @@ <h3>nt_mdt.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt/ruby.html b/nt_mdt/ruby.html
index f22976ea7..3ce619062 100644
--- a/nt_mdt/ruby.html
+++ b/nt_mdt/ruby.html
@@ -105,7 +105,7 @@ <h1>NT-MDT data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A native file format of NT-MDT scientific software. Usually contains
+                <p><p>A native file format of NT-MDT scientific software. Usually contains<br />
 any of:</p>
 <ul>
 <li><a href="https://en.wikipedia.org/wiki/Scanning_probe_microscopy">Scanning probe</a> microscopy scans and spectra</li>
@@ -1430,7 +1430,7 @@ <h3>nt_mdt.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/cpp_stl_11.html b/nt_mdt_pal/cpp_stl_11.html
index 3a4bbc6e4..5d4e03999 100644
--- a/nt_mdt_pal/cpp_stl_11.html
+++ b/nt_mdt_pal/cpp_stl_11.html
@@ -640,7 +640,7 @@ <h3>nt_mdt_pal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/cpp_stl_98.html b/nt_mdt_pal/cpp_stl_98.html
index 11a8db0d9..d9d7e2da1 100644
--- a/nt_mdt_pal/cpp_stl_98.html
+++ b/nt_mdt_pal/cpp_stl_98.html
@@ -684,7 +684,7 @@ <h3>nt_mdt_pal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/csharp.html b/nt_mdt_pal/csharp.html
index 819beeb39..d3bdcaea1 100644
--- a/nt_mdt_pal/csharp.html
+++ b/nt_mdt_pal/csharp.html
@@ -500,7 +500,7 @@ <h3>NtMdtPal.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/go.html b/nt_mdt_pal/go.html
index 93836782e..7c69aad98 100644
--- a/nt_mdt_pal/go.html
+++ b/nt_mdt_pal/go.html
@@ -529,7 +529,7 @@ <h3>nt_mdt_pal.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/graphviz.html b/nt_mdt_pal/graphviz.html
index 56b49acf6..17f1416ac 100644
--- a/nt_mdt_pal/graphviz.html
+++ b/nt_mdt_pal/graphviz.html
@@ -329,7 +329,7 @@ <h3>nt_mdt_pal.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/index.html b/nt_mdt_pal/index.html
index d68a9d794..075ae30e4 100644
--- a/nt_mdt_pal/index.html
+++ b/nt_mdt_pal/index.html
@@ -329,7 +329,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/java.html b/nt_mdt_pal/java.html
index 6307ae536..568ba88a5 100644
--- a/nt_mdt_pal/java.html
+++ b/nt_mdt_pal/java.html
@@ -523,7 +523,7 @@ <h3>NtMdtPal.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/javascript.html b/nt_mdt_pal/javascript.html
index 06e0d31d5..3a4c06bda 100644
--- a/nt_mdt_pal/javascript.html
+++ b/nt_mdt_pal/javascript.html
@@ -427,7 +427,7 @@ <h3>NtMdtPal.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/lua.html b/nt_mdt_pal/lua.html
index 81845a0ae..ddd7e257a 100644
--- a/nt_mdt_pal/lua.html
+++ b/nt_mdt_pal/lua.html
@@ -366,7 +366,7 @@ <h3>nt_mdt_pal.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/nim.html b/nt_mdt_pal/nim.html
index d7038fc14..569a16608 100644
--- a/nt_mdt_pal/nim.html
+++ b/nt_mdt_pal/nim.html
@@ -425,7 +425,7 @@ <h3>nt_mdt_pal.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/perl.html b/nt_mdt_pal/perl.html
index f59f76858..21b0d6da5 100644
--- a/nt_mdt_pal/perl.html
+++ b/nt_mdt_pal/perl.html
@@ -551,7 +551,7 @@ <h3>NtMdtPal.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/php.html b/nt_mdt_pal/php.html
index 6d1f3fd31..6f0814b5c 100644
--- a/nt_mdt_pal/php.html
+++ b/nt_mdt_pal/php.html
@@ -421,7 +421,7 @@ <h3>NtMdtPal.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/python.html b/nt_mdt_pal/python.html
index e14394062..9892c663f 100644
--- a/nt_mdt_pal/python.html
+++ b/nt_mdt_pal/python.html
@@ -385,7 +385,7 @@ <h3>nt_mdt_pal.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/nt_mdt_pal/ruby.html b/nt_mdt_pal/ruby.html
index f6bc8de9f..4a65170b8 100644
--- a/nt_mdt_pal/ruby.html
+++ b/nt_mdt_pal/ruby.html
@@ -426,7 +426,7 @@ <h3>nt_mdt_pal.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/cpp_stl_11.html b/ogg/cpp_stl_11.html
index 3708a6df0..8dab00f5f 100644
--- a/ogg/cpp_stl_11.html
+++ b/ogg/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -623,7 +623,7 @@ <h3>ogg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/cpp_stl_98.html b/ogg/cpp_stl_98.html
index c92242413..631f8d294 100644
--- a/ogg/cpp_stl_98.html
+++ b/ogg/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -649,7 +649,7 @@ <h3>ogg.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/csharp.html b/ogg/csharp.html
index 964afe7c0..e95c03e09 100644
--- a/ogg/csharp.html
+++ b/ogg/csharp.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -525,7 +525,7 @@ <h3>Ogg.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/go.html b/ogg/go.html
index a3a42d595..3d9a5d6bd 100644
--- a/ogg/go.html
+++ b/ogg/go.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -519,7 +519,7 @@ <h3>ogg.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/graphviz.html b/ogg/graphviz.html
index 902618275..97233d819 100644
--- a/ogg/graphviz.html
+++ b/ogg/graphviz.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -325,7 +325,7 @@ <h3>ogg.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/index.html b/ogg/index.html
index 883ab827c..1c2cc86d0 100644
--- a/ogg/index.html
+++ b/ogg/index.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -380,7 +380,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/java.html b/ogg/java.html
index ffa5d6614..9241588d7 100644
--- a/ogg/java.html
+++ b/ogg/java.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -535,7 +535,7 @@ <h3>Ogg.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/javascript.html b/ogg/javascript.html
index 60d5f3b7d..2be8acde3 100644
--- a/ogg/javascript.html
+++ b/ogg/javascript.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -479,7 +479,7 @@ <h3>Ogg.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/lua.html b/ogg/lua.html
index ffb132b26..a77099857 100644
--- a/ogg/lua.html
+++ b/ogg/lua.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -406,7 +406,7 @@ <h3>ogg.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/nim.html b/ogg/nim.html
index 1a4bac045..2507076c9 100644
--- a/ogg/nim.html
+++ b/ogg/nim.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -464,7 +464,7 @@ <h3>ogg.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/perl.html b/ogg/perl.html
index 790ea7862..f3c5796cc 100644
--- a/ogg/perl.html
+++ b/ogg/perl.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -451,7 +451,7 @@ <h3>Ogg.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/php.html b/ogg/php.html
index 75bed9bd5..713bc6b69 100644
--- a/ogg/php.html
+++ b/ogg/php.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -456,7 +456,7 @@ <h3>Ogg.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/python.html b/ogg/python.html
index 20cbd0976..26d285786 100644
--- a/ogg/python.html
+++ b/ogg/python.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -396,7 +396,7 @@ <h3>ogg.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ogg/ruby.html b/ogg/ruby.html
index 2251581ca..c39b647f5 100644
--- a/ogg/ruby.html
+++ b/ogg/ruby.html
@@ -105,13 +105,13 @@ <h1>Ogg media container file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ogg is a popular media container format, which provides basic
-streaming / buffering mechanisms and is content-agnostic. Most
-popular codecs that are used within Ogg streams are Vorbis (thus
+                <p><p>Ogg is a popular media container format, which provides basic<br />
+streaming / buffering mechanisms and is content-agnostic. Most<br />
+popular codecs that are used within Ogg streams are Vorbis (thus<br />
 making Ogg/Vorbis streams) and Theora (Ogg/Theora).</p>
-<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,
-or one can jump into arbitrary stream location and scan for &quot;OggS&quot;
-sync code to find the beginning of a new Ogg page and continue
+<p>Ogg stream is a sequence Ogg pages. They can be read sequentially,<br />
+or one can jump into arbitrary stream location and scan for &quot;OggS&quot;<br />
+sync code to find the beginning of a new Ogg page and continue<br />
 decoding the stream contents from that one.</p>
 </p>
             </div>
@@ -467,7 +467,7 @@ <h3>ogg.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/cpp_stl_11.html b/openpgp_message/cpp_stl_11.html
index 92136bcdf..234c5cd92 100644
--- a/openpgp_message/cpp_stl_11.html
+++ b/openpgp_message/cpp_stl_11.html
@@ -2461,7 +2461,7 @@ <h3>openpgp_message.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/cpp_stl_98.html b/openpgp_message/cpp_stl_98.html
index 49991580d..bb3c0d794 100644
--- a/openpgp_message/cpp_stl_98.html
+++ b/openpgp_message/cpp_stl_98.html
@@ -2715,7 +2715,7 @@ <h3>openpgp_message.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/csharp.html b/openpgp_message/csharp.html
index 065b2738b..d2ae348ea 100644
--- a/openpgp_message/csharp.html
+++ b/openpgp_message/csharp.html
@@ -1684,7 +1684,7 @@ <h3>OpenpgpMessage.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/go.html b/openpgp_message/go.html
index 1e702d7d1..7fd1c6612 100644
--- a/openpgp_message/go.html
+++ b/openpgp_message/go.html
@@ -2087,7 +2087,7 @@ <h3>openpgp_message.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/graphviz.html b/openpgp_message/graphviz.html
index 166b2200d..3cbc206ac 100644
--- a/openpgp_message/graphviz.html
+++ b/openpgp_message/graphviz.html
@@ -715,7 +715,7 @@ <h3>openpgp_message.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/index.html b/openpgp_message/index.html
index 0f11c73ef..b8ce97ba1 100644
--- a/openpgp_message/index.html
+++ b/openpgp_message/index.html
@@ -771,7 +771,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/java.html b/openpgp_message/java.html
index e8542117d..7592125b4 100644
--- a/openpgp_message/java.html
+++ b/openpgp_message/java.html
@@ -1936,7 +1936,7 @@ <h3>OpenpgpMessage.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/javascript.html b/openpgp_message/javascript.html
index ef362519c..3fdadc78f 100644
--- a/openpgp_message/javascript.html
+++ b/openpgp_message/javascript.html
@@ -1409,7 +1409,7 @@ <h3>OpenpgpMessage.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/lua.html b/openpgp_message/lua.html
index 00488c959..2ba3a84db 100644
--- a/openpgp_message/lua.html
+++ b/openpgp_message/lua.html
@@ -1140,7 +1140,7 @@ <h3>openpgp_message.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/nim.html b/openpgp_message/nim.html
index b842fb238..2477a8fa7 100644
--- a/openpgp_message/nim.html
+++ b/openpgp_message/nim.html
@@ -1380,7 +1380,7 @@ <h3>openpgp_message.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/perl.html b/openpgp_message/perl.html
index a9f9f283c..7fb48bb52 100644
--- a/openpgp_message/perl.html
+++ b/openpgp_message/perl.html
@@ -2116,7 +2116,7 @@ <h3>OpenpgpMessage.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/php.html b/openpgp_message/php.html
index b06f74cdd..3ed7fe01a 100644
--- a/openpgp_message/php.html
+++ b/openpgp_message/php.html
@@ -1301,7 +1301,7 @@ <h3>OpenpgpMessage.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/python.html b/openpgp_message/python.html
index 20d2d7a8b..d74ac1939 100644
--- a/openpgp_message/python.html
+++ b/openpgp_message/python.html
@@ -1073,7 +1073,7 @@ <h3>openpgp_message.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/openpgp_message/ruby.html b/openpgp_message/ruby.html
index 72f6acc58..26c6cfb03 100644
--- a/openpgp_message/ruby.html
+++ b/openpgp_message/ruby.html
@@ -1165,7 +1165,7 @@ <h3>openpgp_message.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/cpp_stl_11.html b/packet_ppi/cpp_stl_11.html
index b3f832e6c..2888e9af3 100644
--- a/packet_ppi/cpp_stl_11.html
+++ b/packet_ppi/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1285,7 +1285,7 @@ <h3>packet_ppi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/cpp_stl_98.html b/packet_ppi/cpp_stl_98.html
index 525d12923..8959441ae 100644
--- a/packet_ppi/cpp_stl_98.html
+++ b/packet_ppi/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1398,7 +1398,7 @@ <h3>packet_ppi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/csharp.html b/packet_ppi/csharp.html
index 03da93e71..ea1822363 100644
--- a/packet_ppi/csharp.html
+++ b/packet_ppi/csharp.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1005,7 +1005,7 @@ <h3>PacketPpi.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/go.html b/packet_ppi/go.html
index af7442c3c..cf9093318 100644
--- a/packet_ppi/go.html
+++ b/packet_ppi/go.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1136,7 +1136,7 @@ <h3>packet_ppi.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/graphviz.html b/packet_ppi/graphviz.html
index 762bed220..b82ac5aa4 100644
--- a/packet_ppi/graphviz.html
+++ b/packet_ppi/graphviz.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -424,7 +424,7 @@ <h3>packet_ppi.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/index.html b/packet_ppi/index.html
index b26db77e1..94fb9f83d 100644
--- a/packet_ppi/index.html
+++ b/packet_ppi/index.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -572,7 +572,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/java.html b/packet_ppi/java.html
index 3ce74ec7e..a2c46642c 100644
--- a/packet_ppi/java.html
+++ b/packet_ppi/java.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1086,7 +1086,7 @@ <h3>PacketPpi.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/javascript.html b/packet_ppi/javascript.html
index 0f7285752..eee76b22e 100644
--- a/packet_ppi/javascript.html
+++ b/packet_ppi/javascript.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -914,7 +914,7 @@ <h3>PacketPpi.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/lua.html b/packet_ppi/lua.html
index bd1b8474e..3412c78d5 100644
--- a/packet_ppi/lua.html
+++ b/packet_ppi/lua.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -679,7 +679,7 @@ <h3>packet_ppi.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/nim.html b/packet_ppi/nim.html
index ef64fb4c0..ceccb3e4f 100644
--- a/packet_ppi/nim.html
+++ b/packet_ppi/nim.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -876,7 +876,7 @@ <h3>packet_ppi.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/perl.html b/packet_ppi/perl.html
index fa2a522f5..f01468322 100644
--- a/packet_ppi/perl.html
+++ b/packet_ppi/perl.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -1095,7 +1095,7 @@ <h3>PacketPpi.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/php.html b/packet_ppi/php.html
index a09e6c63a..f4bef2cb4 100644
--- a/packet_ppi/php.html
+++ b/packet_ppi/php.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -838,7 +838,7 @@ <h3>PacketPpi.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/python.html b/packet_ppi/python.html
index 171ad50b1..d71109544 100644
--- a/packet_ppi/python.html
+++ b/packet_ppi/python.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -648,7 +648,7 @@ <h3>packet_ppi.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/packet_ppi/ruby.html b/packet_ppi/ruby.html
index 9e3106074..aabc9e111 100644
--- a/packet_ppi/ruby.html
+++ b/packet_ppi/ruby.html
@@ -105,11 +105,11 @@ <h1>packet_ppi:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PPI is a standard for link layer packet encapsulation, proposed as
-generic extensible container to store both captured in-band data and
-out-of-band data. Originally it was developed to provide 802.11n
+                <p><p>PPI is a standard for link layer packet encapsulation, proposed as<br />
+generic extensible container to store both captured in-band data and<br />
+out-of-band data. Originally it was developed to provide 802.11n<br />
 radio information, but can be used for other purposes as well.</p>
-<p>Sample capture:
+<p>Sample capture:<br />
 <a href="https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap">https://wiki.wireshark.org/uploads/27707187aeb30df68e70c8fb9d614981/http.cap</a></p>
 </p>
             </div>
@@ -783,7 +783,7 @@ <h3>packet_ppi.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/cpp_stl_11.html b/pcap/cpp_stl_11.html
index ec70e8d72..86b5224d8 100644
--- a/pcap/cpp_stl_11.html
+++ b/pcap/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -866,7 +866,7 @@ <h3>pcap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/cpp_stl_98.html b/pcap/cpp_stl_98.html
index bb55f8e55..bd37d3583 100644
--- a/pcap/cpp_stl_98.html
+++ b/pcap/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -901,7 +901,7 @@ <h3>pcap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/csharp.html b/pcap/csharp.html
index db276b1c5..054624bff 100644
--- a/pcap/csharp.html
+++ b/pcap/csharp.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -736,7 +736,7 @@ <h3>Pcap.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/go.html b/pcap/go.html
index dac27004d..6067d6275 100644
--- a/pcap/go.html
+++ b/pcap/go.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -757,7 +757,7 @@ <h3>pcap.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/graphviz.html b/pcap/graphviz.html
index c30c2eddb..4dd7b7b80 100644
--- a/pcap/graphviz.html
+++ b/pcap/graphviz.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -338,7 +338,7 @@ <h3>pcap.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/index.html b/pcap/index.html
index 4d0b136fa..64fd21a5e 100644
--- a/pcap/index.html
+++ b/pcap/index.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -569,7 +569,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/java.html b/pcap/java.html
index 02e5fca25..11606dc4e 100644
--- a/pcap/java.html
+++ b/pcap/java.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -769,7 +769,7 @@ <h3>Pcap.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/javascript.html b/pcap/javascript.html
index 3083a7821..c379481cd 100644
--- a/pcap/javascript.html
+++ b/pcap/javascript.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -887,7 +887,7 @@ <h3>Pcap.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/lua.html b/pcap/lua.html
index 91e11c245..9a55d15cb 100644
--- a/pcap/lua.html
+++ b/pcap/lua.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -611,7 +611,7 @@ <h3>pcap.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/nim.html b/pcap/nim.html
index f7fc557f0..676e8c60a 100644
--- a/pcap/nim.html
+++ b/pcap/nim.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -665,7 +665,7 @@ <h3>pcap.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/perl.html b/pcap/perl.html
index 0d86945ed..2f62ac1d5 100644
--- a/pcap/perl.html
+++ b/pcap/perl.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -704,7 +704,7 @@ <h3>Pcap.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/php.html b/pcap/php.html
index d0d69dce9..3297a767a 100644
--- a/pcap/php.html
+++ b/pcap/php.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -641,7 +641,7 @@ <h3>Pcap.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/python.html b/pcap/python.html
index aaa9a3f1c..fb1fc2f66 100644
--- a/pcap/python.html
+++ b/pcap/python.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -627,7 +627,7 @@ <h3>pcap.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcap/ruby.html b/pcap/ruby.html
index fdb92b109..6c653d432 100644
--- a/pcap/ruby.html
+++ b/pcap/ruby.html
@@ -105,9 +105,9 @@ <h1>.pcap / .pcapdump file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving
-network traffic grabbed by network sniffers. It is typically
-produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or
+                <p><p>PCAP (named after libpcap / winpcap) is a popular format for saving<br />
+network traffic grabbed by network sniffers. It is typically<br />
+produced by tools like <a href="https://www.tcpdump.org/">tcpdump</a> or<br />
 <a href="https://www.wireshark.org/">Wireshark</a>.</p>
 </p>
             </div>
@@ -663,7 +663,7 @@ <h3>pcap.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/cpp_stl_11.html b/pcf_font/cpp_stl_11.html
index d4e7e0965..83098c32f 100644
--- a/pcf_font/cpp_stl_11.html
+++ b/pcf_font/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -1296,7 +1296,7 @@ <h3>pcf_font.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/cpp_stl_98.html b/pcf_font/cpp_stl_98.html
index ed7bc0e2c..290d5ca51 100644
--- a/pcf_font/cpp_stl_98.html
+++ b/pcf_font/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -1424,7 +1424,7 @@ <h3>pcf_font.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/csharp.html b/pcf_font/csharp.html
index 1de639bbd..3e485b932 100644
--- a/pcf_font/csharp.html
+++ b/pcf_font/csharp.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -999,7 +999,7 @@ <h3>PcfFont.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/go.html b/pcf_font/go.html
index 6d3ca6246..ae41f78d3 100644
--- a/pcf_font/go.html
+++ b/pcf_font/go.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -1126,7 +1126,7 @@ <h3>pcf_font.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/graphviz.html b/pcf_font/graphviz.html
index 0c6789c11..54c929fbd 100644
--- a/pcf_font/graphviz.html
+++ b/pcf_font/graphviz.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -489,7 +489,7 @@ <h3>pcf_font.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/index.html b/pcf_font/index.html
index bdac1ab48..cdc271f43 100644
--- a/pcf_font/index.html
+++ b/pcf_font/index.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -595,7 +595,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/java.html b/pcf_font/java.html
index 7c08d00f1..cae32522e 100644
--- a/pcf_font/java.html
+++ b/pcf_font/java.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -1016,7 +1016,7 @@ <h3>PcfFont.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/javascript.html b/pcf_font/javascript.html
index 0cd14a381..3929292d8 100644
--- a/pcf_font/javascript.html
+++ b/pcf_font/javascript.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -790,7 +790,7 @@ <h3>PcfFont.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/lua.html b/pcf_font/lua.html
index de19dbbf6..94f4c51f9 100644
--- a/pcf_font/lua.html
+++ b/pcf_font/lua.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -694,7 +694,7 @@ <h3>pcf_font.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/nim.html b/pcf_font/nim.html
index 76f0db44a..484953a6e 100644
--- a/pcf_font/nim.html
+++ b/pcf_font/nim.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -854,7 +854,7 @@ <h3>pcf_font.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/perl.html b/pcf_font/perl.html
index 387daec6f..41611754a 100644
--- a/pcf_font/perl.html
+++ b/pcf_font/perl.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -1018,7 +1018,7 @@ <h3>PcfFont.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/php.html b/pcf_font/php.html
index a0bd3c8cc..866d43685 100644
--- a/pcf_font/php.html
+++ b/pcf_font/php.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -800,7 +800,7 @@ <h3>PcfFont.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/python.html b/pcf_font/python.html
index c8f010a3b..25a49a550 100644
--- a/pcf_font/python.html
+++ b/pcf_font/python.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -685,7 +685,7 @@ <h3>pcf_font.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcf_font/ruby.html b/pcf_font/ruby.html
index 5e75ae330..3dee1ff58 100644
--- a/pcf_font/ruby.html
+++ b/pcf_font/ruby.html
@@ -105,16 +105,16 @@ <h1>Portable Compiled Format (PCF) font:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Portable Compiled Format (PCF) font is a bitmap font format
-originating from X11 Window System. It matches BDF format (which is
-text-based) closely, but instead being binary and
-platform-independent (as opposed to previously used SNF binary
-format) due to introduced features to handle different endianness
+                <p><p>Portable Compiled Format (PCF) font is a bitmap font format<br />
+originating from X11 Window System. It matches BDF format (which is<br />
+text-based) closely, but instead being binary and<br />
+platform-independent (as opposed to previously used SNF binary<br />
+format) due to introduced features to handle different endianness<br />
 and bit order.</p>
-<p>The overall composition of the format is straightforward: it's more
-or less classic directory of type-offset-size pointers, pointing to
-what PCF format calls &quot;tables&quot;. Each table carries a certain
-piece of information related to the font (metadata properties,
+<p>The overall composition of the format is straightforward: it's more<br />
+or less classic directory of type-offset-size pointers, pointing to<br />
+what PCF format calls &quot;tables&quot;. Each table carries a certain<br />
+piece of information related to the font (metadata properties,<br />
 metrics, bitmaps, mapping of glyphs to characters, etc).</p>
 </p>
             </div>
@@ -743,7 +743,7 @@ <h3>pcf_font.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/cpp_stl_11.html b/pcx/cpp_stl_11.html
index 95fc23e1f..9c49b8fcf 100644
--- a/pcx/cpp_stl_11.html
+++ b/pcx/cpp_stl_11.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -727,7 +727,7 @@ <h3>pcx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/cpp_stl_98.html b/pcx/cpp_stl_98.html
index 1f4eb9a5a..ec38ad354 100644
--- a/pcx/cpp_stl_98.html
+++ b/pcx/cpp_stl_98.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -768,7 +768,7 @@ <h3>pcx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/csharp.html b/pcx/csharp.html
index 9395906ed..50911b172 100644
--- a/pcx/csharp.html
+++ b/pcx/csharp.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -583,7 +583,7 @@ <h3>Pcx.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/go.html b/pcx/go.html
index c8efb6472..8311ca29d 100644
--- a/pcx/go.html
+++ b/pcx/go.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -614,7 +614,7 @@ <h3>pcx.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/graphviz.html b/pcx/graphviz.html
index 5a2cfda24..40e31fc56 100644
--- a/pcx/graphviz.html
+++ b/pcx/graphviz.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -359,7 +359,7 @@ <h3>pcx.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/index.html b/pcx/index.html
index f2554d879..c6c7fc080 100644
--- a/pcx/index.html
+++ b/pcx/index.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -394,7 +394,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/java.html b/pcx/java.html
index 088800584..109358bd9 100644
--- a/pcx/java.html
+++ b/pcx/java.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -614,7 +614,7 @@ <h3>Pcx.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/javascript.html b/pcx/javascript.html
index 258402a49..c82634134 100644
--- a/pcx/javascript.html
+++ b/pcx/javascript.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -503,7 +503,7 @@ <h3>Pcx.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/lua.html b/pcx/lua.html
index 176bb22f0..a22608a09 100644
--- a/pcx/lua.html
+++ b/pcx/lua.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -441,7 +441,7 @@ <h3>pcx.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/nim.html b/pcx/nim.html
index 9a0c5cd38..d721a62e3 100644
--- a/pcx/nim.html
+++ b/pcx/nim.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -491,7 +491,7 @@ <h3>pcx.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/perl.html b/pcx/perl.html
index a2c3841f0..ad3062541 100644
--- a/pcx/perl.html
+++ b/pcx/perl.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -596,7 +596,7 @@ <h3>Pcx.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/php.html b/pcx/php.html
index 413b76d81..1c3186378 100644
--- a/pcx/php.html
+++ b/pcx/php.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -481,7 +481,7 @@ <h3>Pcx.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/python.html b/pcx/python.html
index 1339daf95..dfe3daa5c 100644
--- a/pcx/python.html
+++ b/pcx/python.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -467,7 +467,7 @@ <h3>pcx.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx/ruby.html b/pcx/ruby.html
index 679e780d7..d87ebc3b4 100644
--- a/pcx/ruby.html
+++ b/pcx/ruby.html
@@ -105,17 +105,17 @@ <h1>.pcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from
-ZSoft Corporation. Originally, it was a relatively simple 128-byte
-header + uncompressed bitmap format, but latest versions introduced
+                <p><p>PCX is a bitmap image format originally used by PC Paintbrush from<br />
+ZSoft Corporation. Originally, it was a relatively simple 128-byte<br />
+header + uncompressed bitmap format, but latest versions introduced<br />
 more complicated palette support and RLE compression.</p>
-<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus
-it can potentially include transparency. Theoretically, it's
-possible to encode resolution or pixel density in the some of the
-header fields too, but in reality there's no uniform standard for
+<p>There's an option to encode 32-bit or 16-bit RGBA pixels, and thus<br />
+it can potentially include transparency. Theoretically, it's<br />
+possible to encode resolution or pixel density in the some of the<br />
+header fields too, but in reality there's no uniform standard for<br />
 these, so different implementations treat these differently.</p>
-<p>PCX format was never made a formal standard. &quot;ZSoft Corporation
-Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last
+<p>PCX format was never made a formal standard. &quot;ZSoft Corporation<br />
+Technical Reference Manual&quot; for &quot;Image File (.PCX) Format&quot;, last<br />
 updated in 1991, is likely the closest authoritative source.</p>
 </p>
             </div>
@@ -491,7 +491,7 @@ <h3>pcx.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/cpp_stl_11.html b/pcx_dcx/cpp_stl_11.html
index ab39f63d9..a983eaba5 100644
--- a/pcx_dcx/cpp_stl_11.html
+++ b/pcx_dcx/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -531,7 +531,7 @@ <h3>pcx_dcx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/cpp_stl_98.html b/pcx_dcx/cpp_stl_98.html
index ff805d29d..906c5d2ea 100644
--- a/pcx_dcx/cpp_stl_98.html
+++ b/pcx_dcx/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -554,7 +554,7 @@ <h3>pcx_dcx.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/csharp.html b/pcx_dcx/csharp.html
index c3d10b0bf..fea3bee48 100644
--- a/pcx_dcx/csharp.html
+++ b/pcx_dcx/csharp.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -419,7 +419,7 @@ <h3>PcxDcx.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/go.html b/pcx_dcx/go.html
index fbf126286..629f24f89 100644
--- a/pcx_dcx/go.html
+++ b/pcx_dcx/go.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -388,7 +388,7 @@ <h3>pcx_dcx.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/graphviz.html b/pcx_dcx/graphviz.html
index dbe20c209..c84c69662 100644
--- a/pcx_dcx/graphviz.html
+++ b/pcx_dcx/graphviz.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -312,7 +312,7 @@ <h3>pcx_dcx.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/index.html b/pcx_dcx/index.html
index 77cd2759f..17b896366 100644
--- a/pcx_dcx/index.html
+++ b/pcx_dcx/index.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -301,7 +301,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/java.html b/pcx_dcx/java.html
index 6c1956f96..1d22c5fee 100644
--- a/pcx_dcx/java.html
+++ b/pcx_dcx/java.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -425,7 +425,7 @@ <h3>PcxDcx.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/javascript.html b/pcx_dcx/javascript.html
index a116dc3f2..e6728aef5 100644
--- a/pcx_dcx/javascript.html
+++ b/pcx_dcx/javascript.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -391,7 +391,7 @@ <h3>PcxDcx.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/lua.html b/pcx_dcx/lua.html
index 25d048ab4..ecfe4518e 100644
--- a/pcx_dcx/lua.html
+++ b/pcx_dcx/lua.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -347,7 +347,7 @@ <h3>pcx_dcx.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/nim.html b/pcx_dcx/nim.html
index 5954334bd..064c5bd98 100644
--- a/pcx_dcx/nim.html
+++ b/pcx_dcx/nim.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -356,7 +356,7 @@ <h3>pcx_dcx.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/perl.html b/pcx_dcx/perl.html
index 551b1c740..cb8a1749a 100644
--- a/pcx_dcx/perl.html
+++ b/pcx_dcx/perl.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -386,7 +386,7 @@ <h3>PcxDcx.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/php.html b/pcx_dcx/php.html
index 98a286c69..5949a95e3 100644
--- a/pcx_dcx/php.html
+++ b/pcx_dcx/php.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -343,7 +343,7 @@ <h3>PcxDcx.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/python.html b/pcx_dcx/python.html
index 10ce78935..3cad1a6f6 100644
--- a/pcx_dcx/python.html
+++ b/pcx_dcx/python.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -381,7 +381,7 @@ <h3>pcx_dcx.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pcx_dcx/ruby.html b/pcx_dcx/ruby.html
index 906be9698..9a30623b7 100644
--- a/pcx_dcx/ruby.html
+++ b/pcx_dcx/ruby.html
@@ -105,9 +105,9 @@ <h1>.dcx file format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>DCX is a simple extension of PCX image format allowing to bundle
-many PCX images (typically, pages of a document) in one file. It saw
-some limited use in DOS-era fax software, but was largely
+                <p><p>DCX is a simple extension of PCX image format allowing to bundle<br />
+many PCX images (typically, pages of a document) in one file. It saw<br />
+some limited use in DOS-era fax software, but was largely<br />
 superseded with multi-page TIFFs and PDFs since then.</p>
 </p>
             </div>
@@ -379,7 +379,7 @@ <h3>pcx_dcx.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/cpp_stl_11.html b/phar_without_stub/cpp_stl_11.html
index 2af698282..db235b740 100644
--- a/phar_without_stub/cpp_stl_11.html
+++ b/phar_without_stub/cpp_stl_11.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -1299,7 +1299,7 @@ <h3>phar_without_stub.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/cpp_stl_98.html b/phar_without_stub/cpp_stl_98.html
index c401588b5..01277ac1c 100644
--- a/phar_without_stub/cpp_stl_98.html
+++ b/phar_without_stub/cpp_stl_98.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -1391,7 +1391,7 @@ <h3>phar_without_stub.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/csharp.html b/phar_without_stub/csharp.html
index 4e591e07e..23856f5b2 100644
--- a/phar_without_stub/csharp.html
+++ b/phar_without_stub/csharp.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -1019,7 +1019,7 @@ <h3>PharWithoutStub.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/go.html b/phar_without_stub/go.html
index 5f800727b..63cf3abf5 100644
--- a/phar_without_stub/go.html
+++ b/phar_without_stub/go.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -1052,7 +1052,7 @@ <h3>phar_without_stub.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/graphviz.html b/phar_without_stub/graphviz.html
index 2098b6b45..c2235537b 100644
--- a/phar_without_stub/graphviz.html
+++ b/phar_without_stub/graphviz.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -472,7 +472,7 @@ <h3>phar_without_stub.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/index.html b/phar_without_stub/index.html
index 0442c09a8..e26e51105 100644
--- a/phar_without_stub/index.html
+++ b/phar_without_stub/index.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -618,7 +618,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/java.html b/phar_without_stub/java.html
index 82ff91fa8..64f45d0bf 100644
--- a/phar_without_stub/java.html
+++ b/phar_without_stub/java.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -1020,7 +1020,7 @@ <h3>PharWithoutStub.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/javascript.html b/phar_without_stub/javascript.html
index 37e81f6e7..3e67f9473 100644
--- a/phar_without_stub/javascript.html
+++ b/phar_without_stub/javascript.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -849,7 +849,7 @@ <h3>PharWithoutStub.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/lua.html b/phar_without_stub/lua.html
index 9ffead457..dfe281163 100644
--- a/phar_without_stub/lua.html
+++ b/phar_without_stub/lua.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -736,7 +736,7 @@ <h3>phar_without_stub.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/nim.html b/phar_without_stub/nim.html
index e2c4bd2cd..d59a4916c 100644
--- a/phar_without_stub/nim.html
+++ b/phar_without_stub/nim.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -898,7 +898,7 @@ <h3>phar_without_stub.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/perl.html b/phar_without_stub/perl.html
index 8b85010e2..67a725fa0 100644
--- a/phar_without_stub/perl.html
+++ b/phar_without_stub/perl.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -864,7 +864,7 @@ <h3>PharWithoutStub.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/php.html b/phar_without_stub/php.html
index 21f081d18..322e18baf 100644
--- a/phar_without_stub/php.html
+++ b/phar_without_stub/php.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -867,7 +867,7 @@ <h3>PharWithoutStub.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/python.html b/phar_without_stub/python.html
index 2535d788c..728cf41a4 100644
--- a/phar_without_stub/python.html
+++ b/phar_without_stub/python.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -669,7 +669,7 @@ <h3>phar_without_stub.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/phar_without_stub/ruby.html b/phar_without_stub/ruby.html
index f69b679bb..b0bec5a21 100644
--- a/phar_without_stub/ruby.html
+++ b/phar_without_stub/ruby.html
@@ -105,39 +105,39 @@ <h1>PHP phar archive (without stub):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A phar (PHP archive) file. The phar format is a custom archive format
-from the PHP ecosystem that is used to package a complete PHP library
-or application into a single self-contained archive.
-All phar archives start with an executable PHP stub, which can be used to
-allow executing or including phar files as if they were regular PHP scripts.
-PHP 5.3 and later include the phar extension, which adds native support for
+                <p><p>A phar (PHP archive) file. The phar format is a custom archive format<br />
+from the PHP ecosystem that is used to package a complete PHP library<br />
+or application into a single self-contained archive.<br />
+All phar archives start with an executable PHP stub, which can be used to<br />
+allow executing or including phar files as if they were regular PHP scripts.<br />
+PHP 5.3 and later include the phar extension, which adds native support for<br />
 reading and manipulating phar files.</p>
-<p>The phar format was originally developed as part of the PEAR library
-PHP_Archive, first released in 2005. Later, a native PHP extension
-named &quot;phar&quot; was developed, which was first released on PECL in 2007,
-and is included with PHP 5.3 and later. The phar extension has effectively
-superseded the PHP_Archive library, which has not been updated since 2010.
-The phar extension is also no longer released independently on PECL;
+<p>The phar format was originally developed as part of the PEAR library<br />
+PHP_Archive, first released in 2005. Later, a native PHP extension<br />
+named &quot;phar&quot; was developed, which was first released on PECL in 2007,<br />
+and is included with PHP 5.3 and later. The phar extension has effectively<br />
+superseded the PHP_Archive library, which has not been updated since 2010.<br />
+The phar extension is also no longer released independently on PECL;<br />
 it is now developed and released as part of PHP itself.</p>
-<p>Because of current limitations in Kaitai Struct
-(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),
-the executable PHP stub that precedes the rest of the archive is not handled
-by this spec. Before parsing a phar using this spec, the stub must be
+<p>Because of current limitations in Kaitai Struct<br />
+(seekaitai-io/kaitai_struct#158 and kaitai-io/kaitai_struct#538),<br />
+the executable PHP stub that precedes the rest of the archive is not handled<br />
+by this spec. Before parsing a phar using this spec, the stub must be<br />
 removed manually.</p>
-<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code>
-(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,
-and an optional line terminator). The stub termination sequence is
-immediately followed by the remaining parts of the phar format,
+<p>A phar's stub is terminated by the special token <code>__HALT_COMPILER();</code><br />
+(which may be followed by at most one space, the PHP tag end <code>?&gt;</code>,<br />
+and an optional line terminator). The stub termination sequence is<br />
+immediately followed by the remaining parts of the phar format,<br />
 as described in this spec.</p>
-<p>The phar stub usually contains code that loads the phar and runs
-a contained PHP file, but this is not required. A minimal valid phar stub
-is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute
-the phar directly, but still allows loading or manipulating it using the
+<p>The phar stub usually contains code that loads the phar and runs<br />
+a contained PHP file, but this is not required. A minimal valid phar stub<br />
+is <code>&lt;?php __HALT_COMPILER();</code> - such a stub makes it impossible to execute<br />
+the phar directly, but still allows loading or manipulating it using the<br />
 phar extension.</p>
-<p>Note: The phar format does not specify any encoding for text fields
-(stub, alias name, and all file names), so these fields may contain arbitrary
-binary data. The actual text encoding used in a specific phar file usually
-depends on the application that created the phar, and on the
+<p>Note: The phar format does not specify any encoding for text fields<br />
+(stub, alias name, and all file names), so these fields may contain arbitrary<br />
+binary data. The actual text encoding used in a specific phar file usually<br />
+depends on the application that created the phar, and on the<br />
 standard encoding of the system on which the phar was created.</p>
 </p>
             </div>
@@ -787,7 +787,7 @@ <h3>phar_without_stub.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/cpp_stl_11.html b/php_serialized_value/cpp_stl_11.html
index 6bedafa3e..9ae22f542 100644
--- a/php_serialized_value/cpp_stl_11.html
+++ b/php_serialized_value/cpp_stl_11.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1457,7 +1457,7 @@ <h3>php_serialized_value.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/cpp_stl_98.html b/php_serialized_value/cpp_stl_98.html
index 56b1200b0..c9ce5c19f 100644
--- a/php_serialized_value/cpp_stl_98.html
+++ b/php_serialized_value/cpp_stl_98.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1570,7 +1570,7 @@ <h3>php_serialized_value.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/csharp.html b/php_serialized_value/csharp.html
index 6a8198bf7..ec969f7be 100644
--- a/php_serialized_value/csharp.html
+++ b/php_serialized_value/csharp.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1152,7 +1152,7 @@ <h3>PhpSerializedValue.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/go.html b/php_serialized_value/go.html
index 587c10f93..a0d1a82ac 100644
--- a/php_serialized_value/go.html
+++ b/php_serialized_value/go.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1208,7 +1208,7 @@ <h3>php_serialized_value.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/graphviz.html b/php_serialized_value/graphviz.html
index 328f1379f..a85e9bbb8 100644
--- a/php_serialized_value/graphviz.html
+++ b/php_serialized_value/graphviz.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -488,7 +488,7 @@ <h3>php_serialized_value.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/index.html b/php_serialized_value/index.html
index 6b579c3b2..448c4bd9e 100644
--- a/php_serialized_value/index.html
+++ b/php_serialized_value/index.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -583,7 +583,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/java.html b/php_serialized_value/java.html
index d96c23ec0..5aa3cc459 100644
--- a/php_serialized_value/java.html
+++ b/php_serialized_value/java.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1179,7 +1179,7 @@ <h3>PhpSerializedValue.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/javascript.html b/php_serialized_value/javascript.html
index 13bba48b3..d3743fc4f 100644
--- a/php_serialized_value/javascript.html
+++ b/php_serialized_value/javascript.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -922,7 +922,7 @@ <h3>PhpSerializedValue.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/lua.html b/php_serialized_value/lua.html
index 9297227fa..cf0ddeb7e 100644
--- a/php_serialized_value/lua.html
+++ b/php_serialized_value/lua.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -776,7 +776,7 @@ <h3>php_serialized_value.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/nim.html b/php_serialized_value/nim.html
index b62fcecfd..123bba22c 100644
--- a/php_serialized_value/nim.html
+++ b/php_serialized_value/nim.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -924,7 +924,7 @@ <h3>php_serialized_value.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/perl.html b/php_serialized_value/perl.html
index 05556180d..191030f75 100644
--- a/php_serialized_value/perl.html
+++ b/php_serialized_value/perl.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -1020,7 +1020,7 @@ <h3>PhpSerializedValue.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/php.html b/php_serialized_value/php.html
index 11a2def5b..460fcfcfc 100644
--- a/php_serialized_value/php.html
+++ b/php_serialized_value/php.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -963,7 +963,7 @@ <h3>PhpSerializedValue.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/python.html b/php_serialized_value/python.html
index 957fbefc7..1749405cc 100644
--- a/php_serialized_value/python.html
+++ b/php_serialized_value/python.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -699,7 +699,7 @@ <h3>php_serialized_value.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/php_serialized_value/ruby.html b/php_serialized_value/ruby.html
index beeea9d5d..09b03303b 100644
--- a/php_serialized_value/ruby.html
+++ b/php_serialized_value/ruby.html
@@ -105,19 +105,19 @@ <h1>Serialized PHP value:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and
-<code>unserialize</code> functions. This format closely mirrors PHP's data model:
-it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),
-associative arrays, objects, and recursive data structures using references.
-The only PHP values not supported by this format are <em>resources</em>,
-which usually correspond to native file or connection handles and cannot be
+                <p><p>A serialized PHP value, in the format used by PHP's built-in <code>serialize</code> and<br />
+<code>unserialize</code> functions. This format closely mirrors PHP's data model:<br />
+it supports all of PHP's scalar types (<code>NULL</code>, booleans, numbers, strings),<br />
+associative arrays, objects, and recursive data structures using references.<br />
+The only PHP values not supported by this format are <em>resources</em>,<br />
+which usually correspond to native file or connection handles and cannot be<br />
 meaningfully serialized.</p>
-<p>There is no official documentation for this data format;
-this spec was created based on the PHP source code and the behavior of
-<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of
-serialized data between PHP versions, but in practice, the format has
-remained fully backwards-compatible - values serialized by an older
-PHP version can be unserialized on any newer PHP version.
+<p>There is no official documentation for this data format;<br />
+this spec was created based on the PHP source code and the behavior of<br />
+<code>serialize</code>/<code>unserialize</code>. PHP makes no guarantees about compatibility of<br />
+serialized data between PHP versions, but in practice, the format has<br />
+remained fully backwards-compatible - values serialized by an older<br />
+PHP version can be unserialized on any newer PHP version.<br />
 This spec supports serialized values from PHP 7.3 or any earlier version.</p>
 </p>
             </div>
@@ -788,7 +788,7 @@ <h3>php_serialized_value.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/cpp_stl_11.html b/pif/cpp_stl_11.html
index 35860d611..174c35f45 100644
--- a/pif/cpp_stl_11.html
+++ b/pif/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -807,7 +807,7 @@ <h3>pif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/cpp_stl_98.html b/pif/cpp_stl_98.html
index 755a41fda..737113125 100644
--- a/pif/cpp_stl_98.html
+++ b/pif/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -848,7 +848,7 @@ <h3>pif.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/csharp.html b/pif/csharp.html
index 345f31ac6..5bea5aa47 100644
--- a/pif/csharp.html
+++ b/pif/csharp.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -653,7 +653,7 @@ <h3>Pif.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/go.html b/pif/go.html
index 633862f94..11c8bc3e0 100644
--- a/pif/go.html
+++ b/pif/go.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -809,7 +809,7 @@ <h3>pif.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/index.html b/pif/index.html
index bb8a4b4d4..b981419e7 100644
--- a/pif/index.html
+++ b/pif/index.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -425,7 +425,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/java.html b/pif/java.html
index 9e3762b78..17d249df6 100644
--- a/pif/java.html
+++ b/pif/java.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -651,7 +651,7 @@ <h3>Pif.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/javascript.html b/pif/javascript.html
index 2161ad802..6a207639d 100644
--- a/pif/javascript.html
+++ b/pif/javascript.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -550,7 +550,7 @@ <h3>Pif.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/lua.html b/pif/lua.html
index 434f2fa1f..e7af685b4 100644
--- a/pif/lua.html
+++ b/pif/lua.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -494,7 +494,7 @@ <h3>pif.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/php.html b/pif/php.html
index a859ac2a8..797b14069 100644
--- a/pif/php.html
+++ b/pif/php.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -524,7 +524,7 @@ <h3>Pif.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/python.html b/pif/python.html
index f5eb5375a..4fb7248df 100644
--- a/pif/python.html
+++ b/pif/python.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -489,7 +489,7 @@ <h3>pif.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/pif/ruby.html b/pif/ruby.html
index a45b4c159..8078bd962 100644
--- a/pif/ruby.html
+++ b/pif/ruby.html
@@ -105,8 +105,8 @@ <h1>Portable Image Format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the
-focus on ease of use (implementation) and small size for embedded
+                <p><p>The Portable Image Format (PIF) is a basic, bitmap-like image format with the<br />
+focus on ease of use (implementation) and small size for embedded<br />
 applications.</p>
 <p>See <a href="https://github.com/gfcwfzkm/PIF-Image-Format">https://github.com/gfcwfzkm/PIF-Image-Format</a> for more info.</p>
 </p>
@@ -494,7 +494,7 @@ <h3>pif.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/cpp_stl_11.html b/png/cpp_stl_11.html
index 6e28591f6..65ab69662 100644
--- a/png/cpp_stl_11.html
+++ b/png/cpp_stl_11.html
@@ -1908,7 +1908,7 @@ <h3>png.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/cpp_stl_98.html b/png/cpp_stl_98.html
index 0065c7364..038b6d6f3 100644
--- a/png/cpp_stl_98.html
+++ b/png/cpp_stl_98.html
@@ -2072,7 +2072,7 @@ <h3>png.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/csharp.html b/png/csharp.html
index 3eb7b159e..203962f79 100644
--- a/png/csharp.html
+++ b/png/csharp.html
@@ -1452,7 +1452,7 @@ <h3>Png.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/go.html b/png/go.html
index 2d5e8767d..a2098f057 100644
--- a/png/go.html
+++ b/png/go.html
@@ -1643,7 +1643,7 @@ <h3>png.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/graphviz.html b/png/graphviz.html
index 1646f52b8..2cb59c3a5 100644
--- a/png/graphviz.html
+++ b/png/graphviz.html
@@ -608,7 +608,7 @@ <h3>png.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/index.html b/png/index.html
index a856412df..4bd4b3595 100644
--- a/png/index.html
+++ b/png/index.html
@@ -705,7 +705,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/java.html b/png/java.html
index edc74db56..1d5f94066 100644
--- a/png/java.html
+++ b/png/java.html
@@ -1578,7 +1578,7 @@ <h3>Png.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/javascript.html b/png/javascript.html
index ba59f85a2..4925dd6a0 100644
--- a/png/javascript.html
+++ b/png/javascript.html
@@ -1115,7 +1115,7 @@ <h3>Png.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/lua.html b/png/lua.html
index 92eed4bc0..7e3f3eaf6 100644
--- a/png/lua.html
+++ b/png/lua.html
@@ -939,7 +939,7 @@ <h3>png.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/nim.html b/png/nim.html
index 68a811691..e9e83b2ba 100644
--- a/png/nim.html
+++ b/png/nim.html
@@ -1205,7 +1205,7 @@ <h3>png.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/perl.html b/png/perl.html
index f1ef2b097..6b33cf751 100644
--- a/png/perl.html
+++ b/png/perl.html
@@ -1531,7 +1531,7 @@ <h3>Png.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/php.html b/png/php.html
index cc5e858e5..7d1e7f1e5 100644
--- a/png/php.html
+++ b/png/php.html
@@ -1135,7 +1135,7 @@ <h3>Png.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/python.html b/png/python.html
index 4f9055939..0bf779cf9 100644
--- a/png/python.html
+++ b/png/python.html
@@ -858,7 +858,7 @@ <h3>png.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/png/ruby.html b/png/ruby.html
index c2e2b2224..cb83cdcf3 100644
--- a/png/ruby.html
+++ b/png/ruby.html
@@ -994,7 +994,7 @@ <h3>png.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/cpp_stl_11.html b/protocol_body/cpp_stl_11.html
index e160dec6a..e143fbe6f 100644
--- a/protocol_body/cpp_stl_11.html
+++ b/protocol_body/cpp_stl_11.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -336,20 +336,20 @@ <h3>protocol_body.h</h3>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;kaitai/kaitaistruct.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&lt;stdint.h&gt;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&lt;memory&gt;</span>
-<span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;tcp_segment.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;udp_datagram.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;ipv4_packet.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;icmp_packet.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;ipv6_packet.h&quot;</span>
+<span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;tcp_segment.h&quot;</span>
 
 <span class="cp">#if KAITAI_STRUCT_VERSION &lt; 9000L</span>
 <span class="cp">#error &quot;Incompatible Kaitai Struct C++/STL API: version 0.9 or later is required&quot;</span>
 <span class="cp">#endif</span>
-<span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">udp_datagram_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">ipv4_packet_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">icmp_packet_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">ipv6_packet_t</span><span class="p">;</span>
+<span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="p">;</span>
 
 <span class="cm">/**</span>
 <span class="cm"> * Protocol body represents particular payload on transport level (OSI</span>
@@ -745,7 +745,7 @@ <h3>protocol_body.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/cpp_stl_98.html b/protocol_body/cpp_stl_98.html
index 8d720cad9..2567ca7f7 100644
--- a/protocol_body/cpp_stl_98.html
+++ b/protocol_body/cpp_stl_98.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -336,20 +336,20 @@ <h3>protocol_body.h</h3>
 
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;kaitai/kaitaistruct.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&lt;stdint.h&gt;</span>
-<span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;tcp_segment.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;udp_datagram.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;ipv4_packet.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;icmp_packet.h&quot;</span>
 <span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;ipv6_packet.h&quot;</span>
+<span class="cp">#include</span><span class="w"> </span><span class="cpf">&quot;tcp_segment.h&quot;</span>
 
 <span class="cp">#if KAITAI_STRUCT_VERSION &lt; 9000L</span>
 <span class="cp">#error &quot;Incompatible Kaitai Struct C++/STL API: version 0.9 or later is required&quot;</span>
 <span class="cp">#endif</span>
-<span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">udp_datagram_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">ipv4_packet_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">icmp_packet_t</span><span class="p">;</span>
 <span class="k">class</span><span class="w"> </span><span class="nc">ipv6_packet_t</span><span class="p">;</span>
+<span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="p">;</span>
 
 <span class="cm">/**</span>
 <span class="cm"> * Protocol body represents particular payload on transport level (OSI</span>
@@ -771,7 +771,7 @@ <h3>protocol_body.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/csharp.html b/protocol_body/csharp.html
index 407563830..99dfb8422 100644
--- a/protocol_body/csharp.html
+++ b/protocol_body/csharp.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -601,7 +601,7 @@ <h3>ProtocolBody.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/go.html b/protocol_body/go.html
index 42f50545a..0adc11d87 100644
--- a/protocol_body/go.html
+++ b/protocol_body/go.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -582,7 +582,7 @@ <h3>protocol_body.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/graphviz.html b/protocol_body/graphviz.html
index b9683ab1d..662fdcd34 100644
--- a/protocol_body/graphviz.html
+++ b/protocol_body/graphviz.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -319,7 +319,7 @@ <h3>protocol_body.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/index.html b/protocol_body/index.html
index c8bd47480..6f579eda7 100644
--- a/protocol_body/index.html
+++ b/protocol_body/index.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -449,7 +449,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/java.html b/protocol_body/java.html
index 8a20cae3b..3c59f2d10 100644
--- a/protocol_body/java.html
+++ b/protocol_body/java.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -627,7 +627,7 @@ <h3>ProtocolBody.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/javascript.html b/protocol_body/javascript.html
index b10b08855..dd3e3f3da 100644
--- a/protocol_body/javascript.html
+++ b/protocol_body/javascript.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -293,13 +293,13 @@ <h3>ProtocolBody.js</h3>
 
 <span class="p">(</span><span class="kd">function</span><span class="w"> </span><span class="p">(</span><span class="nx">root</span><span class="p">,</span><span class="w"> </span><span class="nx">factory</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
 <span class="w">  </span><span class="k">if</span><span class="w"> </span><span class="p">(</span><span class="ow">typeof</span><span class="w"> </span><span class="nx">define</span><span class="w"> </span><span class="o">===</span><span class="w"> </span><span class="s1">&#39;function&#39;</span><span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span><span class="nx">define</span><span class="p">.</span><span class="nx">amd</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
-<span class="w">    </span><span class="nx">define</span><span class="p">([</span><span class="s1">&#39;kaitai-struct/KaitaiStream&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./TcpSegment&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./UdpDatagram&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./Ipv4Packet&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./IcmpPacket&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./Ipv6Packet&#39;</span><span class="p">],</span><span class="w"> </span><span class="nx">factory</span><span class="p">);</span>
+<span class="w">    </span><span class="nx">define</span><span class="p">([</span><span class="s1">&#39;kaitai-struct/KaitaiStream&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./UdpDatagram&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./Ipv4Packet&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./IcmpPacket&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./Ipv6Packet&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;./TcpSegment&#39;</span><span class="p">],</span><span class="w"> </span><span class="nx">factory</span><span class="p">);</span>
 <span class="w">  </span><span class="p">}</span><span class="w"> </span><span class="k">else</span><span class="w"> </span><span class="k">if</span><span class="w"> </span><span class="p">(</span><span class="ow">typeof</span><span class="w"> </span><span class="nx">module</span><span class="w"> </span><span class="o">===</span><span class="w"> </span><span class="s1">&#39;object&#39;</span><span class="w"> </span><span class="o">&amp;&amp;</span><span class="w"> </span><span class="nx">module</span><span class="p">.</span><span class="nx">exports</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
-<span class="w">    </span><span class="nx">module</span><span class="p">.</span><span class="nx">exports</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">factory</span><span class="p">(</span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;kaitai-struct/KaitaiStream&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./TcpSegment&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./UdpDatagram&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./Ipv4Packet&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./IcmpPacket&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./Ipv6Packet&#39;</span><span class="p">));</span>
+<span class="w">    </span><span class="nx">module</span><span class="p">.</span><span class="nx">exports</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">factory</span><span class="p">(</span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;kaitai-struct/KaitaiStream&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./UdpDatagram&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./Ipv4Packet&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./IcmpPacket&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./Ipv6Packet&#39;</span><span class="p">),</span><span class="w"> </span><span class="nx">require</span><span class="p">(</span><span class="s1">&#39;./TcpSegment&#39;</span><span class="p">));</span>
 <span class="w">  </span><span class="p">}</span><span class="w"> </span><span class="k">else</span><span class="w"> </span><span class="p">{</span>
-<span class="w">    </span><span class="nx">root</span><span class="p">.</span><span class="nx">ProtocolBody</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">factory</span><span class="p">(</span><span class="nx">root</span><span class="p">.</span><span class="nx">KaitaiStream</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">TcpSegment</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">UdpDatagram</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">Ipv4Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">IcmpPacket</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">Ipv6Packet</span><span class="p">);</span>
+<span class="w">    </span><span class="nx">root</span><span class="p">.</span><span class="nx">ProtocolBody</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">factory</span><span class="p">(</span><span class="nx">root</span><span class="p">.</span><span class="nx">KaitaiStream</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">UdpDatagram</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">Ipv4Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">IcmpPacket</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">Ipv6Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="p">.</span><span class="nx">TcpSegment</span><span class="p">);</span>
 <span class="w">  </span><span class="p">}</span>
-<span class="p">}(</span><span class="ow">typeof</span><span class="w"> </span><span class="nx">self</span><span class="w"> </span><span class="o">!==</span><span class="w"> </span><span class="s1">&#39;undefined&#39;</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="nx">self</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="kd">function</span><span class="w"> </span><span class="p">(</span><span class="nx">KaitaiStream</span><span class="p">,</span><span class="w"> </span><span class="nx">TcpSegment</span><span class="p">,</span><span class="w"> </span><span class="nx">UdpDatagram</span><span class="p">,</span><span class="w"> </span><span class="nx">Ipv4Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">IcmpPacket</span><span class="p">,</span><span class="w"> </span><span class="nx">Ipv6Packet</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="p">}(</span><span class="ow">typeof</span><span class="w"> </span><span class="nx">self</span><span class="w"> </span><span class="o">!==</span><span class="w"> </span><span class="s1">&#39;undefined&#39;</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="nx">self</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="kd">function</span><span class="w"> </span><span class="p">(</span><span class="nx">KaitaiStream</span><span class="p">,</span><span class="w"> </span><span class="nx">UdpDatagram</span><span class="p">,</span><span class="w"> </span><span class="nx">Ipv4Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">IcmpPacket</span><span class="p">,</span><span class="w"> </span><span class="nx">Ipv6Packet</span><span class="p">,</span><span class="w"> </span><span class="nx">TcpSegment</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
 <span class="cm">/**</span>
 <span class="cm"> * Protocol body represents particular payload on transport level (OSI</span>
 <span class="cm"> * layer 4).</span>
@@ -704,7 +704,7 @@ <h3>ProtocolBody.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/lua.html b/protocol_body/lua.html
index 3c2d31207..1152c4c1d 100644
--- a/protocol_body/lua.html
+++ b/protocol_body/lua.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -259,11 +259,11 @@ <h3>protocol_body.lua</h3>
 <span class="kd">local</span> <span class="n">enum</span> <span class="o">=</span> <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;enum&quot;</span><span class="p">)</span>
 <span class="kd">local</span> <span class="n">utils</span> <span class="o">=</span> <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;utils&quot;</span><span class="p">)</span>
 
-<span class="nb">require</span><span class="p">(</span><span class="s2">&quot;tcp_segment&quot;</span><span class="p">)</span>
 <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;udp_datagram&quot;</span><span class="p">)</span>
 <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;ipv4_packet&quot;</span><span class="p">)</span>
 <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;icmp_packet&quot;</span><span class="p">)</span>
 <span class="nb">require</span><span class="p">(</span><span class="s2">&quot;ipv6_packet&quot;</span><span class="p">)</span>
+<span class="nb">require</span><span class="p">(</span><span class="s2">&quot;tcp_segment&quot;</span><span class="p">)</span>
 <span class="c1">-- </span>
 <span class="c1">-- Protocol body represents particular payload on transport level (OSI</span>
 <span class="c1">-- layer 4).</span>
@@ -506,7 +506,7 @@ <h3>protocol_body.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/nim.html b/protocol_body/nim.html
index fea71d07b..6f6ad1770 100644
--- a/protocol_body/nim.html
+++ b/protocol_body/nim.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -258,11 +258,11 @@ <h3>protocol_body.nim</h3>
 <span class="kn">import</span><span class="w"> </span><span class="o">/</span><span class="n">network</span><span class="o">/</span><span class="n">ipv4_packet</span>
 <span class="kn">import</span><span class="w"> </span><span class="o">/</span><span class="n">network</span><span class="o">/</span><span class="n">ipv6_packet</span>
 
-<span class="kn">import</span><span class="w"> </span><span class="s">&quot;tcp_segment&quot;</span>
 <span class="kn">import</span><span class="w"> </span><span class="s">&quot;udp_datagram&quot;</span>
 <span class="kn">import</span><span class="w"> </span><span class="s">&quot;ipv4_packet&quot;</span>
 <span class="kn">import</span><span class="w"> </span><span class="s">&quot;icmp_packet&quot;</span>
 <span class="kn">import</span><span class="w"> </span><span class="s">&quot;ipv6_packet&quot;</span>
+<span class="kn">import</span><span class="w"> </span><span class="s">&quot;tcp_segment&quot;</span>
 <span class="k">type</span>
 <span class="w">  </span><span class="n">ProtocolBody</span><span class="o">*</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">ref</span><span class="w"> </span><span class="k">object</span><span class="w"> </span><span class="k">of</span><span class="w"> </span><span class="n">KaitaiStruct</span>
 <span class="w">    </span><span class="p">`</span><span class="n">body</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">KaitaiStruct</span>
@@ -536,7 +536,7 @@ <h3>protocol_body.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/perl.html b/protocol_body/perl.html
index c769cae5c..c349d89e7 100644
--- a/protocol_body/perl.html
+++ b/protocol_body/perl.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -255,11 +255,11 @@ <h3>ProtocolBody.pm</h3>
 <span class="k">use</span><span class="w"> </span><span class="nn">strict</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">warnings</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">IO::KaitaiStruct</span><span class="w"> </span><span class="mf">0.009_000</span><span class="p">;</span>
-<span class="k">use</span><span class="w"> </span><span class="nn">TcpSegment</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">UdpDatagram</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">Ipv4Packet</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">IcmpPacket</span><span class="p">;</span>
 <span class="k">use</span><span class="w"> </span><span class="nn">Ipv6Packet</span><span class="p">;</span>
+<span class="k">use</span><span class="w"> </span><span class="nn">TcpSegment</span><span class="p">;</span>
 
 <span class="c1">########################################################################</span>
 <span class="k">package</span><span class="w"> </span><span class="nn">ProtocolBody</span><span class="p">;</span>
@@ -575,7 +575,7 @@ <h3>ProtocolBody.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/php.html b/protocol_body/php.html
index b10a7c856..d3a1116f0 100644
--- a/protocol_body/php.html
+++ b/protocol_body/php.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -516,7 +516,7 @@ <h3>ProtocolBody.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/python.html b/protocol_body/python.html
index 152576a7f..995190cd8 100644
--- a/protocol_body/python.html
+++ b/protocol_body/python.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -304,11 +304,11 @@ <h3>protocol_body.py</h3>
 <span class="k">if</span> <span class="nb">getattr</span><span class="p">(</span><span class="n">kaitaistruct</span><span class="p">,</span> <span class="s1">&#39;API_VERSION&#39;</span><span class="p">,</span> <span class="p">(</span><span class="mi">0</span><span class="p">,</span> <span class="mi">9</span><span class="p">))</span> <span class="o">&lt;</span> <span class="p">(</span><span class="mi">0</span><span class="p">,</span> <span class="mi">9</span><span class="p">):</span>
     <span class="k">raise</span> <span class="ne">Exception</span><span class="p">(</span><span class="s2">&quot;Incompatible Kaitai Struct Python API: 0.9 or later is required, but you have </span><span class="si">%s</span><span class="s2">&quot;</span> <span class="o">%</span> <span class="p">(</span><span class="n">kaitaistruct</span><span class="o">.</span><span class="n">__version__</span><span class="p">))</span>
 
-<span class="kn">import</span> <span class="nn">tcp_segment</span>
 <span class="kn">import</span> <span class="nn">udp_datagram</span>
 <span class="kn">import</span> <span class="nn">ipv4_packet</span>
 <span class="kn">import</span> <span class="nn">icmp_packet</span>
 <span class="kn">import</span> <span class="nn">ipv6_packet</span>
+<span class="kn">import</span> <span class="nn">tcp_segment</span>
 <span class="k">class</span> <span class="nc">ProtocolBody</span><span class="p">(</span><span class="n">KaitaiStruct</span><span class="p">):</span>
 <span class="w">    </span><span class="sd">&quot;&quot;&quot;Protocol body represents particular payload on transport level (OSI</span>
 <span class="sd">    layer 4).</span>
@@ -538,7 +538,7 @@ <h3>protocol_body.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/ruby.html b/protocol_body/ruby.html
index be4902ba2..127ac8aee 100644
--- a/protocol_body/ruby.html
+++ b/protocol_body/ruby.html
@@ -105,15 +105,15 @@ <h1>protocol_body:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Protocol body represents particular payload on transport level (OSI
+                <p><p>Protocol body represents particular payload on transport level (OSI<br />
 layer 4).</p>
-<p>Typically this payload in encapsulated into network level (OSI layer
-3) packet, which includes &quot;protocol number&quot; field that would be used
-to decide what's inside the payload and how to parse it. Thanks to
-IANA's standardization effort, multiple network level use the same
+<p>Typically this payload in encapsulated into network level (OSI layer<br />
+3) packet, which includes &quot;protocol number&quot; field that would be used<br />
+to decide what's inside the payload and how to parse it. Thanks to<br />
+IANA's standardization effort, multiple network level use the same<br />
 IDs for these payloads named &quot;protocol numbers&quot;.</p>
-<p>This is effectively a &quot;router&quot; type: it expects to get protocol
-number as a parameter, and then invokes relevant type parser based
+<p>This is effectively a &quot;router&quot; type: it expects to get protocol<br />
+number as a parameter, and then invokes relevant type parser based<br />
 on that parameter.</p>
 </p>
             </div>
@@ -540,7 +540,7 @@ <h3>protocol_body.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/protocol_body/src/cpp_stl_11/protocol_body.h b/protocol_body/src/cpp_stl_11/protocol_body.h
index c995c0bb6..85bf7da76 100644
--- a/protocol_body/src/cpp_stl_11/protocol_body.h
+++ b/protocol_body/src/cpp_stl_11/protocol_body.h
@@ -5,20 +5,20 @@
 #include "kaitai/kaitaistruct.h"
 #include <stdint.h>
 #include <memory>
-#include "tcp_segment.h"
 #include "udp_datagram.h"
 #include "ipv4_packet.h"
 #include "icmp_packet.h"
 #include "ipv6_packet.h"
+#include "tcp_segment.h"
 
 #if KAITAI_STRUCT_VERSION < 9000L
 #error "Incompatible Kaitai Struct C++/STL API: version 0.9 or later is required"
 #endif
-class tcp_segment_t;
 class udp_datagram_t;
 class ipv4_packet_t;
 class icmp_packet_t;
 class ipv6_packet_t;
+class tcp_segment_t;
 
 /**
  * Protocol body represents particular payload on transport level (OSI
diff --git a/protocol_body/src/cpp_stl_98/protocol_body.h b/protocol_body/src/cpp_stl_98/protocol_body.h
index 61a66e1fa..8647b2396 100644
--- a/protocol_body/src/cpp_stl_98/protocol_body.h
+++ b/protocol_body/src/cpp_stl_98/protocol_body.h
@@ -5,20 +5,20 @@
 
 #include "kaitai/kaitaistruct.h"
 #include <stdint.h>
-#include "tcp_segment.h"
 #include "udp_datagram.h"
 #include "ipv4_packet.h"
 #include "icmp_packet.h"
 #include "ipv6_packet.h"
+#include "tcp_segment.h"
 
 #if KAITAI_STRUCT_VERSION < 9000L
 #error "Incompatible Kaitai Struct C++/STL API: version 0.9 or later is required"
 #endif
-class tcp_segment_t;
 class udp_datagram_t;
 class ipv4_packet_t;
 class icmp_packet_t;
 class ipv6_packet_t;
+class tcp_segment_t;
 
 /**
  * Protocol body represents particular payload on transport level (OSI
diff --git a/protocol_body/src/javascript/ProtocolBody.js b/protocol_body/src/javascript/ProtocolBody.js
index 4974e52cf..0d163bdbd 100644
--- a/protocol_body/src/javascript/ProtocolBody.js
+++ b/protocol_body/src/javascript/ProtocolBody.js
@@ -2,13 +2,13 @@
 
 (function (root, factory) {
   if (typeof define === 'function' && define.amd) {
-    define(['kaitai-struct/KaitaiStream', './TcpSegment', './UdpDatagram', './Ipv4Packet', './IcmpPacket', './Ipv6Packet'], factory);
+    define(['kaitai-struct/KaitaiStream', './UdpDatagram', './Ipv4Packet', './IcmpPacket', './Ipv6Packet', './TcpSegment'], factory);
   } else if (typeof module === 'object' && module.exports) {
-    module.exports = factory(require('kaitai-struct/KaitaiStream'), require('./TcpSegment'), require('./UdpDatagram'), require('./Ipv4Packet'), require('./IcmpPacket'), require('./Ipv6Packet'));
+    module.exports = factory(require('kaitai-struct/KaitaiStream'), require('./UdpDatagram'), require('./Ipv4Packet'), require('./IcmpPacket'), require('./Ipv6Packet'), require('./TcpSegment'));
   } else {
-    root.ProtocolBody = factory(root.KaitaiStream, root.TcpSegment, root.UdpDatagram, root.Ipv4Packet, root.IcmpPacket, root.Ipv6Packet);
+    root.ProtocolBody = factory(root.KaitaiStream, root.UdpDatagram, root.Ipv4Packet, root.IcmpPacket, root.Ipv6Packet, root.TcpSegment);
   }
-}(typeof self !== 'undefined' ? self : this, function (KaitaiStream, TcpSegment, UdpDatagram, Ipv4Packet, IcmpPacket, Ipv6Packet) {
+}(typeof self !== 'undefined' ? self : this, function (KaitaiStream, UdpDatagram, Ipv4Packet, IcmpPacket, Ipv6Packet, TcpSegment) {
 /**
  * Protocol body represents particular payload on transport level (OSI
  * layer 4).
diff --git a/protocol_body/src/lua/protocol_body.lua b/protocol_body/src/lua/protocol_body.lua
index 25ec936a8..a7ad68976 100644
--- a/protocol_body/src/lua/protocol_body.lua
+++ b/protocol_body/src/lua/protocol_body.lua
@@ -7,11 +7,11 @@ require("kaitaistruct")
 local enum = require("enum")
 local utils = require("utils")
 
-require("tcp_segment")
 require("udp_datagram")
 require("ipv4_packet")
 require("icmp_packet")
 require("ipv6_packet")
+require("tcp_segment")
 -- 
 -- Protocol body represents particular payload on transport level (OSI
 -- layer 4).
diff --git a/protocol_body/src/nim/protocol_body.nim b/protocol_body/src/nim/protocol_body.nim
index fac37895a..60883d876 100644
--- a/protocol_body/src/nim/protocol_body.nim
+++ b/protocol_body/src/nim/protocol_body.nim
@@ -6,11 +6,11 @@ import /network/udp_datagram
 import /network/ipv4_packet
 import /network/ipv6_packet
 
-import "tcp_segment"
 import "udp_datagram"
 import "ipv4_packet"
 import "icmp_packet"
 import "ipv6_packet"
+import "tcp_segment"
 type
   ProtocolBody* = ref object of KaitaiStruct
     `body`*: KaitaiStruct
diff --git a/protocol_body/src/perl/ProtocolBody.pm b/protocol_body/src/perl/ProtocolBody.pm
index 3605b8b2c..004028af9 100644
--- a/protocol_body/src/perl/ProtocolBody.pm
+++ b/protocol_body/src/perl/ProtocolBody.pm
@@ -3,11 +3,11 @@
 use strict;
 use warnings;
 use IO::KaitaiStruct 0.009_000;
-use TcpSegment;
 use UdpDatagram;
 use Ipv4Packet;
 use IcmpPacket;
 use Ipv6Packet;
+use TcpSegment;
 
 ########################################################################
 package ProtocolBody;
diff --git a/protocol_body/src/python/protocol_body.py b/protocol_body/src/python/protocol_body.py
index c05cf5621..4477e0960 100644
--- a/protocol_body/src/python/protocol_body.py
+++ b/protocol_body/src/python/protocol_body.py
@@ -8,11 +8,11 @@
 if getattr(kaitaistruct, 'API_VERSION', (0, 9)) < (0, 9):
     raise Exception("Incompatible Kaitai Struct Python API: 0.9 or later is required, but you have %s" % (kaitaistruct.__version__))
 
-import tcp_segment
 import udp_datagram
 import ipv4_packet
 import icmp_packet
 import ipv6_packet
+import tcp_segment
 class ProtocolBody(KaitaiStruct):
     """Protocol body represents particular payload on transport level (OSI
     layer 4).
diff --git a/psx_tim/cpp_stl_11.html b/psx_tim/cpp_stl_11.html
index 5465d0fa2..b15b52880 100644
--- a/psx_tim/cpp_stl_11.html
+++ b/psx_tim/cpp_stl_11.html
@@ -574,7 +574,7 @@ <h3>psx_tim.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/cpp_stl_98.html b/psx_tim/cpp_stl_98.html
index 0a8311ff5..33b3faf47 100644
--- a/psx_tim/cpp_stl_98.html
+++ b/psx_tim/cpp_stl_98.html
@@ -594,7 +594,7 @@ <h3>psx_tim.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/csharp.html b/psx_tim/csharp.html
index 2d97c0fbe..c33a20d94 100644
--- a/psx_tim/csharp.html
+++ b/psx_tim/csharp.html
@@ -468,7 +468,7 @@ <h3>PsxTim.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/go.html b/psx_tim/go.html
index 68e69b595..e27a8110f 100644
--- a/psx_tim/go.html
+++ b/psx_tim/go.html
@@ -443,7 +443,7 @@ <h3>psx_tim.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/graphviz.html b/psx_tim/graphviz.html
index 7217009f1..ae1031f6e 100644
--- a/psx_tim/graphviz.html
+++ b/psx_tim/graphviz.html
@@ -330,7 +330,7 @@ <h3>psx_tim.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/index.html b/psx_tim/index.html
index 2bd8b5127..f501680ec 100644
--- a/psx_tim/index.html
+++ b/psx_tim/index.html
@@ -326,7 +326,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/java.html b/psx_tim/java.html
index 86d303825..615a15867 100644
--- a/psx_tim/java.html
+++ b/psx_tim/java.html
@@ -475,7 +475,7 @@ <h3>PsxTim.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/javascript.html b/psx_tim/javascript.html
index 752fc7daa..0fa29de7d 100644
--- a/psx_tim/javascript.html
+++ b/psx_tim/javascript.html
@@ -423,7 +423,7 @@ <h3>PsxTim.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/lua.html b/psx_tim/lua.html
index b051b681c..e25149134 100644
--- a/psx_tim/lua.html
+++ b/psx_tim/lua.html
@@ -369,7 +369,7 @@ <h3>psx_tim.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/nim.html b/psx_tim/nim.html
index 1f5351c41..52d4e616b 100644
--- a/psx_tim/nim.html
+++ b/psx_tim/nim.html
@@ -395,7 +395,7 @@ <h3>psx_tim.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/perl.html b/psx_tim/perl.html
index 9770c174b..d983e6645 100644
--- a/psx_tim/perl.html
+++ b/psx_tim/perl.html
@@ -439,7 +439,7 @@ <h3>PsxTim.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/php.html b/psx_tim/php.html
index eed08e057..9cb061a92 100644
--- a/psx_tim/php.html
+++ b/psx_tim/php.html
@@ -379,7 +379,7 @@ <h3>PsxTim.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/python.html b/psx_tim/python.html
index abc04e5bb..903c9b718 100644
--- a/psx_tim/python.html
+++ b/psx_tim/python.html
@@ -407,7 +407,7 @@ <h3>psx_tim.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/psx_tim/ruby.html b/psx_tim/ruby.html
index 7af9b105a..38c14f126 100644
--- a/psx_tim/ruby.html
+++ b/psx_tim/ruby.html
@@ -409,7 +409,7 @@ <h3>psx_tim.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/csharp.html b/python_pickle/csharp.html
index 71b303dab..d04cf87bc 100644
--- a/python_pickle/csharp.html
+++ b/python_pickle/csharp.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1400,7 +1400,7 @@ <h3>PythonPickle.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/go.html b/python_pickle/go.html
index 0a3714cfe..fa1efc8d9 100644
--- a/python_pickle/go.html
+++ b/python_pickle/go.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1562,7 +1562,7 @@ <h3>python_pickle.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/graphviz.html b/python_pickle/graphviz.html
index 790820685..4d7aef266 100644
--- a/python_pickle/graphviz.html
+++ b/python_pickle/graphviz.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -633,7 +633,7 @@ <h3>python_pickle.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/index.html b/python_pickle/index.html
index 8da2f370a..f7d73e7f5 100644
--- a/python_pickle/index.html
+++ b/python_pickle/index.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -904,7 +904,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/java.html b/python_pickle/java.html
index f325e109e..1fb6763ed 100644
--- a/python_pickle/java.html
+++ b/python_pickle/java.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1519,7 +1519,7 @@ <h3>PythonPickle.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/javascript.html b/python_pickle/javascript.html
index 256d8af8d..8120094ed 100644
--- a/python_pickle/javascript.html
+++ b/python_pickle/javascript.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1180,7 +1180,7 @@ <h3>PythonPickle.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/lua.html b/python_pickle/lua.html
index 0ffe42488..aee4097a3 100644
--- a/python_pickle/lua.html
+++ b/python_pickle/lua.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -937,7 +937,7 @@ <h3>python_pickle.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/nim.html b/python_pickle/nim.html
index 0a08b5f47..1d74c6da2 100644
--- a/python_pickle/nim.html
+++ b/python_pickle/nim.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1162,7 +1162,7 @@ <h3>python_pickle.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/perl.html b/python_pickle/perl.html
index 07f64204d..d1f07c166 100644
--- a/python_pickle/perl.html
+++ b/python_pickle/perl.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1452,7 +1452,7 @@ <h3>PythonPickle.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/php.html b/python_pickle/php.html
index 93a0ca9b9..df0daf634 100644
--- a/python_pickle/php.html
+++ b/python_pickle/php.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -1360,7 +1360,7 @@ <h3>PythonPickle.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/python.html b/python_pickle/python.html
index 8d8a69ebb..09c356362 100644
--- a/python_pickle/python.html
+++ b/python_pickle/python.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -904,7 +904,7 @@ <h3>python_pickle.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pickle/ruby.html b/python_pickle/ruby.html
index 916411ab7..76df23fc3 100644
--- a/python_pickle/ruby.html
+++ b/python_pickle/ruby.html
@@ -105,28 +105,28 @@ <h1>Python pickle serialization format:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence
+                <p><p>Python Pickle format serializes Python objects to a byte stream, as a sequence<br />
 of operations to run on the Pickle Virtual Machine.</p>
-<p>The format is mostly implementation defined, there is no formal specification.
-Pickle data types are closely coupled to the Python object model.
-Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)
-are serialised using dedicated Pickle opcodes.
-Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are
-serialised by encoding the name of a constructor callable.
-They are deserialised by importing that constructor, and calling it.
-So, unpickling an arbitrary pickle, using the Python's stdlib pickle module
+<p>The format is mostly implementation defined, there is no formal specification.<br />
+Pickle data types are closely coupled to the Python object model.<br />
+Python singletons, and most builtin types (e.g. <code>None</code>, <code>int</code>,<code>dict</code>, <code>list</code>)<br />
+are serialised using dedicated Pickle opcodes.<br />
+Other builtin types, and all classes  (e.g. <code>set</code>, <code>datetime.datetime</code>) are<br />
+serialised by encoding the name of a constructor callable.<br />
+They are deserialised by importing that constructor, and calling it.<br />
+So, unpickling an arbitrary pickle, using the Python's stdlib pickle module<br />
 can cause arbitrary code execution.</p>
-<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.
+<p>Pickle format has evolved with Python, later protocols add opcodes &amp; types.<br />
 Later Python releases can pickle to or unpickle from any earlier protocol.</p>
 <ul>
 <li>Protocol 0: ASCII clean, no explicit version, fields are '\n' terminated.</li>
 <li>Protocol 1: Binary, no explicit version, first length prefixed types.</li>
-<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.
+<li>Protocol 2 (<a href="https://peps.python.org/pep-0307/">PEP 307</a>): Python 2.3+.<br />
 Explicit versioning, more length prefixed types.</li>
 <li>Protocol 3: Python 3.0+. Dedicated opcodes for <code>bytes</code> objects.</li>
-<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.
+<li>Protocol 4 (<a href="https://peps.python.org/pep-3154/">PEP 3154</a>): Python 3.4+.<br />
 Opcodes for 64 bit strings, framing, <code>set</code>.</li>
-<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:
+<li>Protocol 5 (<a href="https://peps.python.org/pep-0574/">PEP 574</a>): Python 3.8+:<br />
 Opcodes for <code>bytearray</code> and out of band data</li>
 </ul>
 </p>
@@ -970,7 +970,7 @@ <h3>python_pickle.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/csharp.html b/python_pyc_27/csharp.html
index a70678498..a1c66c1f5 100644
--- a/python_pyc_27/csharp.html
+++ b/python_pyc_27/csharp.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -968,7 +968,7 @@ <h3>PythonPyc27.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/go.html b/python_pyc_27/go.html
index 16344dc61..07b9f15b9 100644
--- a/python_pyc_27/go.html
+++ b/python_pyc_27/go.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -1018,7 +1018,7 @@ <h3>python_pyc_27.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/graphviz.html b/python_pyc_27/graphviz.html
index 6465ca700..6905800df 100644
--- a/python_pyc_27/graphviz.html
+++ b/python_pyc_27/graphviz.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -471,7 +471,7 @@ <h3>python_pyc_27.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/index.html b/python_pyc_27/index.html
index 66e318e2d..90e4dd1b6 100644
--- a/python_pyc_27/index.html
+++ b/python_pyc_27/index.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -587,7 +587,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/java.html b/python_pyc_27/java.html
index f296a9a12..a5646fa69 100644
--- a/python_pyc_27/java.html
+++ b/python_pyc_27/java.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -1084,7 +1084,7 @@ <h3>PythonPyc27.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/javascript.html b/python_pyc_27/javascript.html
index 0e0c1adb3..cd5a78cfa 100644
--- a/python_pyc_27/javascript.html
+++ b/python_pyc_27/javascript.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -944,7 +944,7 @@ <h3>PythonPyc27.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/lua.html b/python_pyc_27/lua.html
index 76ad9bae2..67d99a89f 100644
--- a/python_pyc_27/lua.html
+++ b/python_pyc_27/lua.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -715,7 +715,7 @@ <h3>python_pyc_27.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/nim.html b/python_pyc_27/nim.html
index 6111ea6e1..c2f47feb2 100644
--- a/python_pyc_27/nim.html
+++ b/python_pyc_27/nim.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -809,7 +809,7 @@ <h3>python_pyc_27.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/perl.html b/python_pyc_27/perl.html
index c741a2b70..2e22e507f 100644
--- a/python_pyc_27/perl.html
+++ b/python_pyc_27/perl.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -1149,7 +1149,7 @@ <h3>PythonPyc27.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/php.html b/python_pyc_27/php.html
index 24480c9a9..5ad239a0d 100644
--- a/python_pyc_27/php.html
+++ b/python_pyc_27/php.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -787,7 +787,7 @@ <h3>PythonPyc27.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/python.html b/python_pyc_27/python.html
index 090d37f9a..2bf1273a1 100644
--- a/python_pyc_27/python.html
+++ b/python_pyc_27/python.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -712,7 +712,7 @@ <h3>python_pyc_27.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/python_pyc_27/ruby.html b/python_pyc_27/ruby.html
index a994ffe44..e43e62965 100644
--- a/python_pyc_27/ruby.html
+++ b/python_pyc_27/ruby.html
@@ -105,11 +105,11 @@ <h1>.pyc file format of Python:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Python interpreter runs .py files in 2 step process: first, it
-produces bytecode, which it then executes. Translation of .py source
-into bytecode is time-consuming, so Python dumps compiled bytecode
+                <p><p>Python interpreter runs .py files in 2 step process: first, it<br />
+produces bytecode, which it then executes. Translation of .py source<br />
+into bytecode is time-consuming, so Python dumps compiled bytecode<br />
 into .pyc files, to be reused from cache at later time if possible.</p>
-<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with
+<p>.pyc file is essentially a raw dump of <code>py_object</code> (see <code>body</code>) with<br />
 a simple header prepended.</p>
 </p>
             </div>
@@ -754,7 +754,7 @@ <h3>python_pyc_27.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/cpp_stl_11.html b/quake2_md2/cpp_stl_11.html
index 6a0f7effc..7137ec2bd 100644
--- a/quake2_md2/cpp_stl_11.html
+++ b/quake2_md2/cpp_stl_11.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -1429,7 +1429,7 @@ <h3>quake2_md2.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/csharp.html b/quake2_md2/csharp.html
index bc41af02c..619ccdae4 100644
--- a/quake2_md2/csharp.html
+++ b/quake2_md2/csharp.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -1122,7 +1122,7 @@ <h3>Quake2Md2.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/go.html b/quake2_md2/go.html
index 76aeb5691..4ff374a49 100644
--- a/quake2_md2/go.html
+++ b/quake2_md2/go.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -1179,7 +1179,7 @@ <h3>quake2_md2.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/graphviz.html b/quake2_md2/graphviz.html
index 525220a29..550085fa0 100644
--- a/quake2_md2/graphviz.html
+++ b/quake2_md2/graphviz.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -575,7 +575,7 @@ <h3>quake2_md2.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/index.html b/quake2_md2/index.html
index 3bfc38db2..9dc771400 100644
--- a/quake2_md2/index.html
+++ b/quake2_md2/index.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -752,7 +752,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/java.html b/quake2_md2/java.html
index 07aa63f6c..d53b219cc 100644
--- a/quake2_md2/java.html
+++ b/quake2_md2/java.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -1056,7 +1056,7 @@ <h3>Quake2Md2.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/javascript.html b/quake2_md2/javascript.html
index f7af516e4..f84a0fa12 100644
--- a/quake2_md2/javascript.html
+++ b/quake2_md2/javascript.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -852,7 +852,7 @@ <h3>Quake2Md2.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/lua.html b/quake2_md2/lua.html
index 1f4b87fd4..e008dd7d7 100644
--- a/quake2_md2/lua.html
+++ b/quake2_md2/lua.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -824,7 +824,7 @@ <h3>quake2_md2.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/nim.html b/quake2_md2/nim.html
index 454eea469..217d8e69f 100644
--- a/quake2_md2/nim.html
+++ b/quake2_md2/nim.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -918,7 +918,7 @@ <h3>quake2_md2.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/perl.html b/quake2_md2/perl.html
index 37672bccf..de682e21e 100644
--- a/quake2_md2/perl.html
+++ b/quake2_md2/perl.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -1082,7 +1082,7 @@ <h3>Quake2Md2.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/php.html b/quake2_md2/php.html
index 4725b468d..7dd901c56 100644
--- a/quake2_md2/php.html
+++ b/quake2_md2/php.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -845,7 +845,7 @@ <h3>Quake2Md2.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/python.html b/quake2_md2/python.html
index 43cb23be5..267a74250 100644
--- a/quake2_md2/python.html
+++ b/quake2_md2/python.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -805,7 +805,7 @@ <h3>quake2_md2.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake2_md2/ruby.html b/quake2_md2/ruby.html
index f68d0b1b1..1661b810b 100644
--- a/quake2_md2/ruby.html
+++ b/quake2_md2/ruby.html
@@ -106,58 +106,58 @@ <h1>Quake II player model (version 8):
         <div class="row">
             <div class="col-md-8">
                 <p><p>The MD2 format is used for 3D animated models in id Sofware's Quake II.</p>
-<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code>
-(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in
-model space. Each vertex has the same topological &quot;meaning&quot; across frames, in
-terms of triangle and texture info; it just varies in position and normal for
+<p>A model consists of named <code>frames</code>, each with the same number of <code>vertices</code><br />
+(<code>vertices_per_frame</code>). Each such vertex has a <code>position</code> and <code>normal</code> in<br />
+model space. Each vertex has the same topological &quot;meaning&quot; across frames, in<br />
+terms of triangle and texture info; it just varies in position and normal for<br />
 animation purposes.</p>
-<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via
-<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three
-<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into
-global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code>
-ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with
+<p>How the vertices form triangles is defined via disjoint <code>triangles</code> or via<br />
+<code>gl_cmds</code> (which allows strip and fan topology). Each triangle contains three<br />
+<code>vertex_indices</code> into frame vertices, and three <code>tex_point_indices</code> into<br />
+global <code>tex_coords</code>. Each texture point has pixel coords <code>s_px</code> and <code>t_px</code><br />
+ranging from 0 to <code>skin_{width,height}_px</code> respectively, along with<br />
 <code>{s,t}_normalized</code> ranging from 0 to 1 for your convenience.</p>
-<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along
-with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0
+<p>A GL command has a <code>primitive</code> type (<code>TRIANGLE_FAN</code> or <code>TRIANGLE_STRIP</code>) along<br />
+with some <code>vertices</code>. Each GL vertex contains <code>tex_coords_normalized</code> from 0<br />
 to 1, and a <code>vertex_index</code> into frame vertices.</p>
-<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.
-However, this is empty for many models, in which case it is up to the client
-(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the
+<p>A model may also contain <code>skins</code>, which are just file paths to PCX images.<br />
+However, this is empty for many models, in which case it is up to the client<br />
+(e.g. Q2PRO) to offer skins some other way (e.g. by similar filename in the<br />
 current directory).</p>
-<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used
-for different animations. Each frame has a standard <code>name</code> for humans, but the
-client just uses their index and the name can be arbitrary. The name, start
-frame index and frame count of each animation can be looked up in the arrays
-<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This
+<p>There are 198 <code>frames</code> in total, partitioned into a fixed set of ranges used<br />
+for different animations. Each frame has a standard <code>name</code> for humans, but the<br />
+client just uses their index and the name can be arbitrary. The name, start<br />
+frame index and frame count of each animation can be looked up in the arrays<br />
+<code>anim_names</code>, <code>anim_start_indices</code>, and <code>anim_num_frames</code> respectively. This<br />
 information is summarized in the following table:</p>
-<pre><code>|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
-|:--------:|--------:|:-------|:-------------------------------------------------------|
-|    0-39  |   stand | 01-40  | Idle animation                                         |
-|   40-45  |     run | 1-6    | Full run cycle                                         |
-|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
-|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
-|   58-61  |   pain2 | 01-04  |                                                        |
-|   62-65  |   pain3 | 01-04  |                                                        |
-|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
-|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
-|   84-94  |  salute | 01-11  |                                                        |
-|   95-111 |   taunt | 01-17  |                                                        |
-|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
-|  123-134 |   point | 01-12  |                                                        |
-|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
-|  154-159 |  crwalk | 1-6    |                                                        |
-|  160-168 | crattak | 1-9    |                                                        |
-|  169-172 |  crpain | 1-4    |                                                        |
-|  173-177 | crdeath | 1-5    |                                                        |
-|  178-183 |  death1 | 01-06  |                                                        |
-|  184-189 |  death2 | 01-06  |                                                        |
-|  190-197 |  death3 | 01-08  |                                                        |
-</code></pre>
-<p>The above are filled in for player models; for the separate weapon models,
-the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown
-during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is
-the same except that the <code>wave</code> frames are blank (according to the default
-female model files). This is likely due to its dual use as a grenade throw
+<pre style="background-color:#2b303b;"><code><span style="color:#c0c5ce;">|   INDEX  |    NAME | SUFFIX | NOTES                                                  |
+</span><span style="color:#c0c5ce;">|:--------:|--------:|:-------|:-------------------------------------------------------|
+</span><span style="color:#c0c5ce;">|    0-39  |   stand | 01-40  | Idle animation                                         |
+</span><span style="color:#c0c5ce;">|   40-45  |     run | 1-6    | Full run cycle                                         |
+</span><span style="color:#c0c5ce;">|   46-53  |  attack | 1-8    | Shoot, reload; some weapons just repeat 1st few frames |
+</span><span style="color:#c0c5ce;">|   54-57  |   pain1 | 01-04  | Q2Pro also uses this for switching weapons             |
+</span><span style="color:#c0c5ce;">|   58-61  |   pain2 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   62-65  |   pain3 | 01-04  |                                                        |
+</span><span style="color:#c0c5ce;">|   66-71  |    jump | 1-6    | Starts at height and lands on feet                     |
+</span><span style="color:#c0c5ce;">|   72-83  |    flip | 01-12  | Flipoff, i.e. middle finger                            |
+</span><span style="color:#c0c5ce;">|   84-94  |  salute | 01-11  |                                                        |
+</span><span style="color:#c0c5ce;">|   95-111 |   taunt | 01-17  |                                                        |
+</span><span style="color:#c0c5ce;">|  112-122 |    wave | 01-11  | Q2Pro plays this backwards for a handgrenade toss      |
+</span><span style="color:#c0c5ce;">|  123-134 |   point | 01-12  |                                                        |
+</span><span style="color:#c0c5ce;">|  135-153 |  crstnd | 01-19  | Idle while crouching                                   |
+</span><span style="color:#c0c5ce;">|  154-159 |  crwalk | 1-6    |                                                        |
+</span><span style="color:#c0c5ce;">|  160-168 | crattak | 1-9    |                                                        |
+</span><span style="color:#c0c5ce;">|  169-172 |  crpain | 1-4    |                                                        |
+</span><span style="color:#c0c5ce;">|  173-177 | crdeath | 1-5    |                                                        |
+</span><span style="color:#c0c5ce;">|  178-183 |  death1 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  184-189 |  death2 | 01-06  |                                                        |
+</span><span style="color:#c0c5ce;">|  190-197 |  death3 | 01-08  |                                                        |
+</span></code></pre>
+<p>The above are filled in for player models; for the separate weapon models,<br />
+the final frame is 173 &quot;g_view&quot; (unknown purpose) since weapons aren't shown<br />
+during death animations. <code>a_grenades.md2</code>, the handgrenade weapon model, is<br />
+the same except that the <code>wave</code> frames are blank (according to the default<br />
+female model files). This is likely due to its dual use as a grenade throw<br />
 animation where this model must leave the player's model.</p>
 </p>
             </div>
@@ -789,7 +789,7 @@ <h3>quake2_md2.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/cpp_stl_11.html b/quake_mdl/cpp_stl_11.html
index 15b051d82..3552fac43 100644
--- a/quake_mdl/cpp_stl_11.html
+++ b/quake_mdl/cpp_stl_11.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -1176,7 +1176,7 @@ <h3>quake_mdl.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/cpp_stl_98.html b/quake_mdl/cpp_stl_98.html
index 0c9bba696..f93f995c2 100644
--- a/quake_mdl/cpp_stl_98.html
+++ b/quake_mdl/cpp_stl_98.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -1307,7 +1307,7 @@ <h3>quake_mdl.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/csharp.html b/quake_mdl/csharp.html
index 1b3c9648d..95ab3307e 100644
--- a/quake_mdl/csharp.html
+++ b/quake_mdl/csharp.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -872,7 +872,7 @@ <h3>QuakeMdl.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/go.html b/quake_mdl/go.html
index 2e1a322ba..fee28e1f4 100644
--- a/quake_mdl/go.html
+++ b/quake_mdl/go.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -931,7 +931,7 @@ <h3>quake_mdl.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/graphviz.html b/quake_mdl/graphviz.html
index 8ef1fc5b2..149a7ad6a 100644
--- a/quake_mdl/graphviz.html
+++ b/quake_mdl/graphviz.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -463,7 +463,7 @@ <h3>quake_mdl.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/index.html b/quake_mdl/index.html
index e77d0f238..c00081d6d 100644
--- a/quake_mdl/index.html
+++ b/quake_mdl/index.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -520,7 +520,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/java.html b/quake_mdl/java.html
index 26a06e651..d5edb77b2 100644
--- a/quake_mdl/java.html
+++ b/quake_mdl/java.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -887,7 +887,7 @@ <h3>QuakeMdl.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/javascript.html b/quake_mdl/javascript.html
index f09e34c55..f8e8d993d 100644
--- a/quake_mdl/javascript.html
+++ b/quake_mdl/javascript.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -688,7 +688,7 @@ <h3>QuakeMdl.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/lua.html b/quake_mdl/lua.html
index c90870096..3890f09b4 100644
--- a/quake_mdl/lua.html
+++ b/quake_mdl/lua.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -611,7 +611,7 @@ <h3>quake_mdl.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/nim.html b/quake_mdl/nim.html
index b75f307a7..f9aa204ad 100644
--- a/quake_mdl/nim.html
+++ b/quake_mdl/nim.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -723,7 +723,7 @@ <h3>quake_mdl.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/perl.html b/quake_mdl/perl.html
index 406288f05..e9c6b7398 100644
--- a/quake_mdl/perl.html
+++ b/quake_mdl/perl.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -927,7 +927,7 @@ <h3>QuakeMdl.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/php.html b/quake_mdl/php.html
index 4d8c51777..4e59f9793 100644
--- a/quake_mdl/php.html
+++ b/quake_mdl/php.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -705,7 +705,7 @@ <h3>QuakeMdl.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/python.html b/quake_mdl/python.html
index 277d20b8c..41a45f0db 100644
--- a/quake_mdl/python.html
+++ b/quake_mdl/python.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -614,7 +614,7 @@ <h3>quake_mdl.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_mdl/ruby.html b/quake_mdl/ruby.html
index 75797e4c7..a23dca3d6 100644
--- a/quake_mdl/ruby.html
+++ b/quake_mdl/ruby.html
@@ -105,37 +105,37 @@ <h1>Quake 1 (idtech2) model format (MDL version 6):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Quake 1 model format is used to store 3D models completely with
-textures and animations used in the game. Quake 1 engine
-(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used
+                <p><p>Quake 1 model format is used to store 3D models completely with<br />
+textures and animations used in the game. Quake 1 engine<br />
+(retroactively named &quot;idtech2&quot;) is a popular 3D engine first used<br />
 for Quake game by id Software in 1996.</p>
-<p>Model is constructed traditionally from vertices in 3D space, faces
-which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and
-texture UV mapping information. As opposed to more modern,
-bones-based animation formats, Quake model was animated by changing
+<p>Model is constructed traditionally from vertices in 3D space, faces<br />
+which connect vertices, textures (&quot;skins&quot;, i.e. 2D bitmaps) and<br />
+texture UV mapping information. As opposed to more modern,<br />
+bones-based animation formats, Quake model was animated by changing<br />
 locations of all vertices it included in 3D space, frame by frame.</p>
 <p>File format stores:</p>
 <ul>
-<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a
-texture. Every model can have multiple skins — e.g. these can be
-switched to depict various levels of damage to the
-monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake
-palette, subject to lighting and gamma adjustment when rendering
+<li>&quot;Skins&quot; — effectively 2D bitmaps which will be used as a<br />
+texture. Every model can have multiple skins — e.g. these can be<br />
+switched to depict various levels of damage to the<br />
+monsters. Bitmaps are 8-bit-per-pixel, indexed in global Quake<br />
+palette, subject to lighting and gamma adjustment when rendering<br />
 in the game using colormap technique.</li>
-<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to
+<li>&quot;Texture coordinates&quot; — UV coordinates, mapping 3D vertices to<br />
 skin coordinates.</li>
 <li>&quot;Triangles&quot; — triangular faces connecting 3D vertices.</li>
-<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more
-than one frame, thus allowing representation of different frames
+<li>&quot;Frames&quot; — locations of vertices in 3D space; can include more<br />
+than one frame, thus allowing representation of different frames<br />
 for animation purposes.</li>
 </ul>
-<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias
-PowerAnimator</a>,
-precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,
-3D-related part of Quake model format followed closely Alias TRI
-format, and Quake development utilities included a converter from Alias
+<p>Originally, 3D geometry for models for Quake was designed in <a href="https://en.wikipedia.org/wiki/PowerAnimator">Alias<br />
+PowerAnimator</a>,<br />
+precursor of modern day Autodesk Maya and Autodesk Alias. Therefore,<br />
+3D-related part of Quake model format followed closely Alias TRI<br />
+format, and Quake development utilities included a converter from Alias<br />
 TRI (<code>modelgen</code>).</p>
-<p>Skins (textures) where prepared as LBM bitmaps with the help from
+<p>Skins (textures) where prepared as LBM bitmaps with the help from<br />
 <code>texmap</code> utility in the same development utilities toolkit.</p>
 </p>
             </div>
@@ -671,7 +671,7 @@ <h3>quake_mdl.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/cpp_stl_11.html b/quake_pak/cpp_stl_11.html
index 41c7bf54d..a7457104a 100644
--- a/quake_pak/cpp_stl_11.html
+++ b/quake_pak/cpp_stl_11.html
@@ -597,7 +597,7 @@ <h3>quake_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/cpp_stl_98.html b/quake_pak/cpp_stl_98.html
index 35a2abae2..e10d28c25 100644
--- a/quake_pak/cpp_stl_98.html
+++ b/quake_pak/cpp_stl_98.html
@@ -629,7 +629,7 @@ <h3>quake_pak.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/csharp.html b/quake_pak/csharp.html
index 25d087251..771e95568 100644
--- a/quake_pak/csharp.html
+++ b/quake_pak/csharp.html
@@ -470,7 +470,7 @@ <h3>QuakePak.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/go.html b/quake_pak/go.html
index 1d1a3faf9..4c9cb49d7 100644
--- a/quake_pak/go.html
+++ b/quake_pak/go.html
@@ -468,7 +468,7 @@ <h3>quake_pak.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/graphviz.html b/quake_pak/graphviz.html
index cb8a778f7..fda3ad88d 100644
--- a/quake_pak/graphviz.html
+++ b/quake_pak/graphviz.html
@@ -333,7 +333,7 @@ <h3>quake_pak.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/index.html b/quake_pak/index.html
index c72425d56..e63849301 100644
--- a/quake_pak/index.html
+++ b/quake_pak/index.html
@@ -315,7 +315,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/java.html b/quake_pak/java.html
index c433da8f5..871b3eec2 100644
--- a/quake_pak/java.html
+++ b/quake_pak/java.html
@@ -475,7 +475,7 @@ <h3>QuakePak.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/javascript.html b/quake_pak/javascript.html
index e20352030..43336808a 100644
--- a/quake_pak/javascript.html
+++ b/quake_pak/javascript.html
@@ -420,7 +420,7 @@ <h3>QuakePak.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/lua.html b/quake_pak/lua.html
index ae4be4789..f3f3d37b6 100644
--- a/quake_pak/lua.html
+++ b/quake_pak/lua.html
@@ -375,7 +375,7 @@ <h3>quake_pak.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/nim.html b/quake_pak/nim.html
index 02526c88e..341d632d8 100644
--- a/quake_pak/nim.html
+++ b/quake_pak/nim.html
@@ -396,7 +396,7 @@ <h3>quake_pak.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/perl.html b/quake_pak/perl.html
index 761251e95..dd2d6798b 100644
--- a/quake_pak/perl.html
+++ b/quake_pak/perl.html
@@ -460,7 +460,7 @@ <h3>QuakePak.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/php.html b/quake_pak/php.html
index c66a2c9c0..2e795de0d 100644
--- a/quake_pak/php.html
+++ b/quake_pak/php.html
@@ -375,7 +375,7 @@ <h3>QuakePak.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/python.html b/quake_pak/python.html
index 20c9e1ce9..43265da05 100644
--- a/quake_pak/python.html
+++ b/quake_pak/python.html
@@ -407,7 +407,7 @@ <h3>quake_pak.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quake_pak/ruby.html b/quake_pak/ruby.html
index bb2ed8bc0..0c60c72ca 100644
--- a/quake_pak/ruby.html
+++ b/quake_pak/ruby.html
@@ -406,7 +406,7 @@ <h3>quake_pak.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/cpp_stl_11.html b/quicktime_mov/cpp_stl_11.html
index 45a48364a..5aeca94d2 100644
--- a/quicktime_mov/cpp_stl_11.html
+++ b/quicktime_mov/cpp_stl_11.html
@@ -1364,7 +1364,7 @@ <h3>quicktime_mov.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/cpp_stl_98.html b/quicktime_mov/cpp_stl_98.html
index 257de3de2..13796e43c 100644
--- a/quicktime_mov/cpp_stl_98.html
+++ b/quicktime_mov/cpp_stl_98.html
@@ -1444,7 +1444,7 @@ <h3>quicktime_mov.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/csharp.html b/quicktime_mov/csharp.html
index 039a824ef..d4d04c615 100644
--- a/quicktime_mov/csharp.html
+++ b/quicktime_mov/csharp.html
@@ -1120,7 +1120,7 @@ <h3>QuicktimeMov.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/go.html b/quicktime_mov/go.html
index 716829b18..7b9f9449c 100644
--- a/quicktime_mov/go.html
+++ b/quicktime_mov/go.html
@@ -1345,7 +1345,7 @@ <h3>quicktime_mov.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/graphviz.html b/quicktime_mov/graphviz.html
index 2f2e8573e..3609ab095 100644
--- a/quicktime_mov/graphviz.html
+++ b/quicktime_mov/graphviz.html
@@ -439,7 +439,7 @@ <h3>quicktime_mov.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/index.html b/quicktime_mov/index.html
index 5e1f555b0..13ca3e5df 100644
--- a/quicktime_mov/index.html
+++ b/quicktime_mov/index.html
@@ -748,7 +748,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/java.html b/quicktime_mov/java.html
index 12ffc9d6e..fa77b7412 100644
--- a/quicktime_mov/java.html
+++ b/quicktime_mov/java.html
@@ -1184,7 +1184,7 @@ <h3>QuicktimeMov.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/javascript.html b/quicktime_mov/javascript.html
index 582343af5..c77173742 100644
--- a/quicktime_mov/javascript.html
+++ b/quicktime_mov/javascript.html
@@ -1237,7 +1237,7 @@ <h3>QuicktimeMov.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/lua.html b/quicktime_mov/lua.html
index 6cf64048c..c039bae01 100644
--- a/quicktime_mov/lua.html
+++ b/quicktime_mov/lua.html
@@ -849,7 +849,7 @@ <h3>quicktime_mov.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/nim.html b/quicktime_mov/nim.html
index c5ef5e3b0..44bae6ac6 100644
--- a/quicktime_mov/nim.html
+++ b/quicktime_mov/nim.html
@@ -1013,7 +1013,7 @@ <h3>quicktime_mov.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/perl.html b/quicktime_mov/perl.html
index a43a7acac..06d3b3628 100644
--- a/quicktime_mov/perl.html
+++ b/quicktime_mov/perl.html
@@ -1181,7 +1181,7 @@ <h3>QuicktimeMov.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/php.html b/quicktime_mov/php.html
index 8ee8968b4..90c868958 100644
--- a/quicktime_mov/php.html
+++ b/quicktime_mov/php.html
@@ -964,7 +964,7 @@ <h3>QuicktimeMov.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/python.html b/quicktime_mov/python.html
index bd052ee5d..8b9fcaaa0 100644
--- a/quicktime_mov/python.html
+++ b/quicktime_mov/python.html
@@ -831,7 +831,7 @@ <h3>quicktime_mov.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/quicktime_mov/ruby.html b/quicktime_mov/ruby.html
index aec186c47..2284027b4 100644
--- a/quicktime_mov/ruby.html
+++ b/quicktime_mov/ruby.html
@@ -930,7 +930,7 @@ <h3>quicktime_mov.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/cpp_stl_11.html b/rar/cpp_stl_11.html
index 9c045fb99..7e3385006 100644
--- a/rar/cpp_stl_11.html
+++ b/rar/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -970,7 +970,7 @@ <h3>rar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/cpp_stl_98.html b/rar/cpp_stl_98.html
index 929de9c42..26515d632 100644
--- a/rar/cpp_stl_98.html
+++ b/rar/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -1023,7 +1023,7 @@ <h3>rar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/csharp.html b/rar/csharp.html
index f07294f89..8c7b0ee20 100644
--- a/rar/csharp.html
+++ b/rar/csharp.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -749,7 +749,7 @@ <h3>Rar.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/go.html b/rar/go.html
index 6fc7a57ee..252af1dd6 100644
--- a/rar/go.html
+++ b/rar/go.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -790,7 +790,7 @@ <h3>rar.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/graphviz.html b/rar/graphviz.html
index 1e39bae87..498292abc 100644
--- a/rar/graphviz.html
+++ b/rar/graphviz.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -400,7 +400,7 @@ <h3>rar.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/index.html b/rar/index.html
index 05c9ec85f..ac746c820 100644
--- a/rar/index.html
+++ b/rar/index.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/java.html b/rar/java.html
index 8f8fe282d..e00865fb7 100644
--- a/rar/java.html
+++ b/rar/java.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -792,7 +792,7 @@ <h3>Rar.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/javascript.html b/rar/javascript.html
index 39000e585..8933608d5 100644
--- a/rar/javascript.html
+++ b/rar/javascript.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -660,7 +660,7 @@ <h3>Rar.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/lua.html b/rar/lua.html
index ce5dcd7d3..142084971 100644
--- a/rar/lua.html
+++ b/rar/lua.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -548,7 +548,7 @@ <h3>rar.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/nim.html b/rar/nim.html
index cc76ee5ce..ad3c4271e 100644
--- a/rar/nim.html
+++ b/rar/nim.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -640,7 +640,7 @@ <h3>rar.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/perl.html b/rar/perl.html
index e51ef44de..7c5040645 100644
--- a/rar/perl.html
+++ b/rar/perl.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -687,7 +687,7 @@ <h3>Rar.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/php.html b/rar/php.html
index 060621f02..d13a5b9f0 100644
--- a/rar/php.html
+++ b/rar/php.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -628,7 +628,7 @@ <h3>Rar.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/python.html b/rar/python.html
index 6d39bf884..6db40fd73 100644
--- a/rar/python.html
+++ b/rar/python.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -530,7 +530,7 @@ <h3>rar.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rar/ruby.html b/rar/ruby.html
index 071ff6cdf..39086b89a 100644
--- a/rar/ruby.html
+++ b/rar/ruby.html
@@ -105,12 +105,12 @@ <h1>RAR (Roshall ARchiver) archive files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>RAR is a archive format used by popular proprietary RAR archiver,
-created by Eugene Roshal. There are two major versions of format
+                <p><p>RAR is a archive format used by popular proprietary RAR archiver,<br />
+created by Eugene Roshal. There are two major versions of format<br />
 (v1.5-4.0 and RAR v5+).</p>
-<p>File format essentially consists of a linear sequence of
-blocks. Each block has fixed header and custom body (that depends on
-block type), so it's possible to skip block even if one doesn't know
+<p>File format essentially consists of a linear sequence of<br />
+blocks. Each block has fixed header and custom body (that depends on<br />
+block type), so it's possible to skip block even if one doesn't know<br />
 how to process a certain block type.</p>
 </p>
             </div>
@@ -604,7 +604,7 @@ <h3>rar.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/cpp_stl_11.html b/regf/cpp_stl_11.html
index 9b4a89780..833578e08 100644
--- a/regf/cpp_stl_11.html
+++ b/regf/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1452,7 +1452,7 @@ <h3>regf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/cpp_stl_98.html b/regf/cpp_stl_98.html
index 206d18647..be933986b 100644
--- a/regf/cpp_stl_98.html
+++ b/regf/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1604,7 +1604,7 @@ <h3>regf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/csharp.html b/regf/csharp.html
index 2e60b0d60..f1c132ecd 100644
--- a/regf/csharp.html
+++ b/regf/csharp.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1088,7 +1088,7 @@ <h3>Regf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/go.html b/regf/go.html
index aca7c9a06..05713a159 100644
--- a/regf/go.html
+++ b/regf/go.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1307,7 +1307,7 @@ <h3>regf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/graphviz.html b/regf/graphviz.html
index b66b7657f..4f1d49e38 100644
--- a/regf/graphviz.html
+++ b/regf/graphviz.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -540,7 +540,7 @@ <h3>regf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/index.html b/regf/index.html
index 47ff3c637..f879a720b 100644
--- a/regf/index.html
+++ b/regf/index.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -571,7 +571,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/java.html b/regf/java.html
index f2a4ad40e..ed53e718c 100644
--- a/regf/java.html
+++ b/regf/java.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1196,7 +1196,7 @@ <h3>Regf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/javascript.html b/regf/javascript.html
index 684e0b39b..8327b2836 100644
--- a/regf/javascript.html
+++ b/regf/javascript.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -832,7 +832,7 @@ <h3>Regf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/lua.html b/regf/lua.html
index 6ef4a3bf8..5e4c605f8 100644
--- a/regf/lua.html
+++ b/regf/lua.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -724,7 +724,7 @@ <h3>regf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/nim.html b/regf/nim.html
index a1fa879e8..63f58c7d3 100644
--- a/regf/nim.html
+++ b/regf/nim.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -906,7 +906,7 @@ <h3>regf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/perl.html b/regf/perl.html
index bbb62109a..4bac88bae 100644
--- a/regf/perl.html
+++ b/regf/perl.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -1337,7 +1337,7 @@ <h3>Regf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/php.html b/regf/php.html
index 8850b9d15..be481dffc 100644
--- a/regf/php.html
+++ b/regf/php.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -880,7 +880,7 @@ <h3>Regf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/python.html b/regf/python.html
index ee07fbd69..f204de1ac 100644
--- a/regf/python.html
+++ b/regf/python.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -698,7 +698,7 @@ <h3>regf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/regf/ruby.html b/regf/ruby.html
index 9cfbcd71a..8abf80645 100644
--- a/regf/ruby.html
+++ b/regf/ruby.html
@@ -105,9 +105,9 @@ <h1>Windows registry database:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec allows to parse files used by Microsoft Windows family of
-operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a
-hierarchical database that is used to store system settings (global
+                <p><p>This spec allows to parse files used by Microsoft Windows family of<br />
+operating systems to store parts of its &quot;registry&quot;. &quot;Registry&quot; is a<br />
+hierarchical database that is used to store system settings (global<br />
 configuration, per-user, per-application configuration, etc).</p>
 <p>Typically, registry files are stored in:</p>
 <ul>
@@ -120,7 +120,7 @@ <h1>Windows registry database:
 </ul>
 </li>
 </ul>
-<p>Note that one typically can't access files directly on a mounted
+<p>Note that one typically can't access files directly on a mounted<br />
 filesystem with a running Windows OS.</p>
 </p>
             </div>
@@ -793,7 +793,7 @@ <h3>regf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/cpp_stl_11.html b/renderware_binary_stream/cpp_stl_11.html
index c24367163..c459b28c9 100644
--- a/renderware_binary_stream/cpp_stl_11.html
+++ b/renderware_binary_stream/cpp_stl_11.html
@@ -1941,7 +1941,7 @@ <h3>renderware_binary_stream.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/cpp_stl_98.html b/renderware_binary_stream/cpp_stl_98.html
index eeccb8959..18381e536 100644
--- a/renderware_binary_stream/cpp_stl_98.html
+++ b/renderware_binary_stream/cpp_stl_98.html
@@ -2144,7 +2144,7 @@ <h3>renderware_binary_stream.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/csharp.html b/renderware_binary_stream/csharp.html
index 41c354dd6..45dfefd9b 100644
--- a/renderware_binary_stream/csharp.html
+++ b/renderware_binary_stream/csharp.html
@@ -1397,7 +1397,7 @@ <h3>RenderwareBinaryStream.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/go.html b/renderware_binary_stream/go.html
index 3dc88f44e..96e821d09 100644
--- a/renderware_binary_stream/go.html
+++ b/renderware_binary_stream/go.html
@@ -1621,7 +1621,7 @@ <h3>renderware_binary_stream.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/graphviz.html b/renderware_binary_stream/graphviz.html
index b540f3f59..decfda62c 100644
--- a/renderware_binary_stream/graphviz.html
+++ b/renderware_binary_stream/graphviz.html
@@ -611,7 +611,7 @@ <h3>renderware_binary_stream.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/index.html b/renderware_binary_stream/index.html
index 4c86cae00..a845dbd5d 100644
--- a/renderware_binary_stream/index.html
+++ b/renderware_binary_stream/index.html
@@ -697,7 +697,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/java.html b/renderware_binary_stream/java.html
index 156253d64..fa6fb44d2 100644
--- a/renderware_binary_stream/java.html
+++ b/renderware_binary_stream/java.html
@@ -1465,7 +1465,7 @@ <h3>RenderwareBinaryStream.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/javascript.html b/renderware_binary_stream/javascript.html
index 50127778c..c81611160 100644
--- a/renderware_binary_stream/javascript.html
+++ b/renderware_binary_stream/javascript.html
@@ -1229,7 +1229,7 @@ <h3>RenderwareBinaryStream.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/lua.html b/renderware_binary_stream/lua.html
index 66d8c5610..3cb0b610d 100644
--- a/renderware_binary_stream/lua.html
+++ b/renderware_binary_stream/lua.html
@@ -978,7 +978,7 @@ <h3>renderware_binary_stream.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/nim.html b/renderware_binary_stream/nim.html
index 4a2fce1a2..438f3787d 100644
--- a/renderware_binary_stream/nim.html
+++ b/renderware_binary_stream/nim.html
@@ -1172,7 +1172,7 @@ <h3>renderware_binary_stream.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/perl.html b/renderware_binary_stream/perl.html
index c3657967a..61b8a3266 100644
--- a/renderware_binary_stream/perl.html
+++ b/renderware_binary_stream/perl.html
@@ -1636,7 +1636,7 @@ <h3>RenderwareBinaryStream.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/php.html b/renderware_binary_stream/php.html
index c9b47a00e..e8ecfdddd 100644
--- a/renderware_binary_stream/php.html
+++ b/renderware_binary_stream/php.html
@@ -1071,7 +1071,7 @@ <h3>RenderwareBinaryStream.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/python.html b/renderware_binary_stream/python.html
index afc599c10..24206b83d 100644
--- a/renderware_binary_stream/python.html
+++ b/renderware_binary_stream/python.html
@@ -965,7 +965,7 @@ <h3>renderware_binary_stream.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/renderware_binary_stream/ruby.html b/renderware_binary_stream/ruby.html
index 31b88a26e..9d0086f4d 100644
--- a/renderware_binary_stream/ruby.html
+++ b/renderware_binary_stream/ruby.html
@@ -1000,7 +1000,7 @@ <h3>renderware_binary_stream.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/cpp_stl_11.html b/resource_fork/cpp_stl_11.html
index 7f1dde23e..15d482ef2 100644
--- a/resource_fork/cpp_stl_11.html
+++ b/resource_fork/cpp_stl_11.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1915,7 +1915,7 @@ <h3>resource_fork.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/cpp_stl_98.html b/resource_fork/cpp_stl_98.html
index 601c30ed6..da7c49447 100644
--- a/resource_fork/cpp_stl_98.html
+++ b/resource_fork/cpp_stl_98.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -2055,7 +2055,7 @@ <h3>resource_fork.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/csharp.html b/resource_fork/csharp.html
index 2dbd56827..fd2399f28 100644
--- a/resource_fork/csharp.html
+++ b/resource_fork/csharp.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1558,7 +1558,7 @@ <h3>ResourceFork.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/go.html b/resource_fork/go.html
index ad77dead6..b0509c905 100644
--- a/resource_fork/go.html
+++ b/resource_fork/go.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1740,7 +1740,7 @@ <h3>resource_fork.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/graphviz.html b/resource_fork/graphviz.html
index 1a9025bf4..753416312 100644
--- a/resource_fork/graphviz.html
+++ b/resource_fork/graphviz.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -552,7 +552,7 @@ <h3>resource_fork.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/index.html b/resource_fork/index.html
index 4e79c6af7..af0685028 100644
--- a/resource_fork/index.html
+++ b/resource_fork/index.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -900,7 +900,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/java.html b/resource_fork/java.html
index e06479e07..2adbc7c31 100644
--- a/resource_fork/java.html
+++ b/resource_fork/java.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1522,7 +1522,7 @@ <h3>ResourceFork.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/javascript.html b/resource_fork/javascript.html
index d771b924d..adc8e7402 100644
--- a/resource_fork/javascript.html
+++ b/resource_fork/javascript.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1287,7 +1287,7 @@ <h3>ResourceFork.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/lua.html b/resource_fork/lua.html
index 2efee729b..975831b1d 100644
--- a/resource_fork/lua.html
+++ b/resource_fork/lua.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1114,7 +1114,7 @@ <h3>resource_fork.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/nim.html b/resource_fork/nim.html
index 7cd5fe819..fa88484d1 100644
--- a/resource_fork/nim.html
+++ b/resource_fork/nim.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1435,7 +1435,7 @@ <h3>resource_fork.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/perl.html b/resource_fork/perl.html
index ab3f96c85..04376203c 100644
--- a/resource_fork/perl.html
+++ b/resource_fork/perl.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1161,7 +1161,7 @@ <h3>ResourceFork.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/php.html b/resource_fork/php.html
index 05eb1d358..ee75609e9 100644
--- a/resource_fork/php.html
+++ b/resource_fork/php.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1300,7 +1300,7 @@ <h3>ResourceFork.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/python.html b/resource_fork/python.html
index 713e2cee5..e9f32d342 100644
--- a/resource_fork/python.html
+++ b/resource_fork/python.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -829,7 +829,7 @@ <h3>resource_fork.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/resource_fork/ruby.html b/resource_fork/ruby.html
index 71661ed31..90247c312 100644
--- a/resource_fork/ruby.html
+++ b/resource_fork/ruby.html
@@ -105,38 +105,38 @@ <h1>Macintosh resource fork data:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The data format of Macintosh resource forks,
-used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).
+                <p><p>The data format of Macintosh resource forks,<br />
+used on Classic Mac OS and Mac OS X/macOS to store additional structured data along with a file's main data (the data fork).<br />
 The kinds of data stored in resource forks include:</p>
 <ul>
-<li>Document resources:
+<li>Document resources:<br />
 images, sounds, etc. used by a document</li>
-<li>Application resources:
-graphics, GUI layouts, localizable strings,
+<li>Application resources:<br />
+graphics, GUI layouts, localizable strings,<br />
 and even code used by an application, a library, or system files</li>
-<li>Common metadata:
+<li>Common metadata:<br />
 custom icons and version metadata that could be displayed by the Finder</li>
-<li>Application-specific metadata:
-because resource forks follow a common format,
-other applications can store new metadata in them,
+<li>Application-specific metadata:<br />
+because resource forks follow a common format,<br />
+other applications can store new metadata in them,<br />
 even if the original application does not recognize or understand it</li>
 </ul>
-<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,
-which allows storing resources along with any file.
-Non-Macintosh file systems and protocols have little or no support for resource forks,
-so the resource fork data must be stored in some other way when using such file systems or protocols.
-Various file formats and tools exist for this purpose,
-such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.
-In some cases,
-resource forks are stored as plain data in separate files with a .rsrc extension,
+<p>Macintosh file systems (MFS, HFS, HFS+, APFS) support resource forks natively,<br />
+which allows storing resources along with any file.<br />
+Non-Macintosh file systems and protocols have little or no support for resource forks,<br />
+so the resource fork data must be stored in some other way when using such file systems or protocols.<br />
+Various file formats and tools exist for this purpose,<br />
+such as BinHex, MacBinary, AppleSingle, AppleDouble, or QuickTime RezWack.<br />
+In some cases,<br />
+resource forks are stored as plain data in separate files with a .rsrc extension,<br />
 even on Mac systems that natively support resource forks.</p>
-<p>On modern Mac OS X/macOS systems,
-resource forks are used far less commonly than on classic Mac OS systems,
-because of compatibility issues with other systems and historical limitations in the format.
-Modern macOS APIs and libraries do not use resource forks,
-and the legacy Carbon API that still used them has been deprecated since OS X 10.8.
-Despite this,
-even current macOS systems still use resource forks for certain purposes,
+<p>On modern Mac OS X/macOS systems,<br />
+resource forks are used far less commonly than on classic Mac OS systems,<br />
+because of compatibility issues with other systems and historical limitations in the format.<br />
+Modern macOS APIs and libraries do not use resource forks,<br />
+and the legacy Carbon API that still used them has been deprecated since OS X 10.8.<br />
+Despite this,<br />
+even current macOS systems still use resource forks for certain purposes,<br />
 such as custom file icons.</p>
 </p>
             </div>
@@ -1180,7 +1180,7 @@ <h3>resource_fork.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/cpp_stl_11.html b/respack/cpp_stl_11.html
index 6f08f9574..b84f6fb1f 100644
--- a/respack/cpp_stl_11.html
+++ b/respack/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -472,7 +472,7 @@ <h3>respack.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/cpp_stl_98.html b/respack/cpp_stl_98.html
index a44835a3a..80a2bfa9a 100644
--- a/respack/cpp_stl_98.html
+++ b/respack/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -489,7 +489,7 @@ <h3>respack.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/csharp.html b/respack/csharp.html
index 1ad436086..1dc46ea66 100644
--- a/respack/csharp.html
+++ b/respack/csharp.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -376,7 +376,7 @@ <h3>Respack.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/go.html b/respack/go.html
index 9bdf33166..4da49ee82 100644
--- a/respack/go.html
+++ b/respack/go.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -348,7 +348,7 @@ <h3>respack.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/graphviz.html b/respack/graphviz.html
index 0d31ac78b..5159b0322 100644
--- a/respack/graphviz.html
+++ b/respack/graphviz.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -282,7 +282,7 @@ <h3>respack.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/index.html b/respack/index.html
index 798e43419..80f1830ce 100644
--- a/respack/index.html
+++ b/respack/index.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -270,7 +270,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/java.html b/respack/java.html
index 42fef89f4..b29200c4a 100644
--- a/respack/java.html
+++ b/respack/java.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -389,7 +389,7 @@ <h3>Respack.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/javascript.html b/respack/javascript.html
index 6144f692a..a2abdbef9 100644
--- a/respack/javascript.html
+++ b/respack/javascript.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -351,7 +351,7 @@ <h3>Respack.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/lua.html b/respack/lua.html
index 523e91d49..f254c3d2e 100644
--- a/respack/lua.html
+++ b/respack/lua.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -301,7 +301,7 @@ <h3>respack.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/nim.html b/respack/nim.html
index a496d4c66..2b8a52cf9 100644
--- a/respack/nim.html
+++ b/respack/nim.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -318,7 +318,7 @@ <h3>respack.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/perl.html b/respack/perl.html
index 3524376e1..00429de28 100644
--- a/respack/perl.html
+++ b/respack/perl.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -362,7 +362,7 @@ <h3>Respack.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/php.html b/respack/php.html
index 3b7d8f119..eb1a4282a 100644
--- a/respack/php.html
+++ b/respack/php.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -310,7 +310,7 @@ <h3>Respack.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/python.html b/respack/python.html
index b5f45671d..4d87fbcba 100644
--- a/respack/python.html
+++ b/respack/python.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -335,7 +335,7 @@ <h3>respack.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/respack/ruby.html b/respack/ruby.html
index 4ce6a2b99..2123c9e21 100644
--- a/respack/ruby.html
+++ b/respack/ruby.html
@@ -105,7 +105,7 @@ <h1>ResPack:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad
+                <p><p>Resource file found in CPB firmware archives, mostly used on older CoolPad<br />
 phones and/or tablets. The only observed files are called &quot;ResPack.cfg&quot;.</p>
 </p>
             </div>
@@ -344,7 +344,7 @@ <h3>respack.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/cpp_stl_11.html b/riff/cpp_stl_11.html
index 82bde363f..794678c79 100644
--- a/riff/cpp_stl_11.html
+++ b/riff/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -1209,7 +1209,7 @@ <h3>riff.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/cpp_stl_98.html b/riff/cpp_stl_98.html
index e4f349389..60567f40e 100644
--- a/riff/cpp_stl_98.html
+++ b/riff/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -1301,7 +1301,7 @@ <h3>riff.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/csharp.html b/riff/csharp.html
index 58fe1a961..de3d33ec5 100644
--- a/riff/csharp.html
+++ b/riff/csharp.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -882,7 +882,7 @@ <h3>Riff.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/go.html b/riff/go.html
index 4a0275d6f..c2db4d8ad 100644
--- a/riff/go.html
+++ b/riff/go.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -1019,7 +1019,7 @@ <h3>riff.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/graphviz.html b/riff/graphviz.html
index 4a35a5cc7..9cfeb955c 100644
--- a/riff/graphviz.html
+++ b/riff/graphviz.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -472,7 +472,7 @@ <h3>riff.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/index.html b/riff/index.html
index 460c2bea1..71b8ba55c 100644
--- a/riff/index.html
+++ b/riff/index.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -420,7 +420,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/java.html b/riff/java.html
index cf1c5e181..9636dfe5b 100644
--- a/riff/java.html
+++ b/riff/java.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -832,7 +832,7 @@ <h3>Riff.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/javascript.html b/riff/javascript.html
index 48d1bd785..73c65e137 100644
--- a/riff/javascript.html
+++ b/riff/javascript.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -688,7 +688,7 @@ <h3>Riff.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/lua.html b/riff/lua.html
index 7edb906ff..145ec6e7d 100644
--- a/riff/lua.html
+++ b/riff/lua.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -657,7 +657,7 @@ <h3>riff.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/nim.html b/riff/nim.html
index 460c433ac..2c950a92d 100644
--- a/riff/nim.html
+++ b/riff/nim.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -719,7 +719,7 @@ <h3>riff.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/perl.html b/riff/perl.html
index 66f28d1c7..d866c5742 100644
--- a/riff/perl.html
+++ b/riff/perl.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -810,7 +810,7 @@ <h3>Riff.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/php.html b/riff/php.html
index 731c3f51a..c61a6a901 100644
--- a/riff/php.html
+++ b/riff/php.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -633,7 +633,7 @@ <h3>Riff.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/python.html b/riff/python.html
index 8bbcc8574..822b66415 100644
--- a/riff/python.html
+++ b/riff/python.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -643,7 +643,7 @@ <h3>riff.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/riff/ruby.html b/riff/ruby.html
index 8234b96bd..92727ccb8 100644
--- a/riff/ruby.html
+++ b/riff/ruby.html
@@ -105,10 +105,10 @@ <h1>Resource Interchange File Format (RIFF):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format
-for storing data in tagged chunks. It is primarily used to store multimedia
+                <p><p>The Resource Interchange File Format (RIFF) is a generic file container format<br />
+for storing data in tagged chunks. It is primarily used to store multimedia<br />
 such as sound and video, though it may also be used to store any arbitrary data.</p>
-<p>The Microsoft implementation is mostly known through container formats
+<p>The Microsoft implementation is mostly known through container formats<br />
 like AVI, ANI and WAV, which use RIFF as their basis.</p>
 </p>
             </div>
@@ -609,7 +609,7 @@ <h3>riff.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/cpp_stl_11.html b/rpm/cpp_stl_11.html
index a008a7e20..bce5a5c93 100644
--- a/rpm/cpp_stl_11.html
+++ b/rpm/cpp_stl_11.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -2007,7 +2007,7 @@ <h3>rpm.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/cpp_stl_98.html b/rpm/cpp_stl_98.html
index 2d69cd393..e3c692ccd 100644
--- a/rpm/cpp_stl_98.html
+++ b/rpm/cpp_stl_98.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -2156,7 +2156,7 @@ <h3>rpm.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/csharp.html b/rpm/csharp.html
index dbd821938..9ef239baf 100644
--- a/rpm/csharp.html
+++ b/rpm/csharp.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1515,7 +1515,7 @@ <h3>Rpm.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/graphviz.html b/rpm/graphviz.html
index 207b28a88..5c3b10952 100644
--- a/rpm/graphviz.html
+++ b/rpm/graphviz.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -572,7 +572,7 @@ <h3>rpm.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/index.html b/rpm/index.html
index cf2d9dbbb..349d7dbc4 100644
--- a/rpm/index.html
+++ b/rpm/index.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1769,7 +1769,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/java.html b/rpm/java.html
index b9c8a49ca..94fa764d6 100644
--- a/rpm/java.html
+++ b/rpm/java.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1559,7 +1559,7 @@ <h3>Rpm.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/javascript.html b/rpm/javascript.html
index d69b94aef..69dbb3cb1 100644
--- a/rpm/javascript.html
+++ b/rpm/javascript.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1608,7 +1608,7 @@ <h3>Rpm.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/lua.html b/rpm/lua.html
index b01bc38c7..aa8eb991d 100644
--- a/rpm/lua.html
+++ b/rpm/lua.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1187,7 +1187,7 @@ <h3>rpm.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/nim.html b/rpm/nim.html
index 7968f4a31..1edf921c6 100644
--- a/rpm/nim.html
+++ b/rpm/nim.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1284,7 +1284,7 @@ <h3>rpm.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/perl.html b/rpm/perl.html
index 7c98757f9..a9719bb5b 100644
--- a/rpm/perl.html
+++ b/rpm/perl.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1592,7 +1592,7 @@ <h3>Rpm.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/php.html b/rpm/php.html
index 51ee5ec90..48ea8ee04 100644
--- a/rpm/php.html
+++ b/rpm/php.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1567,7 +1567,7 @@ <h3>Rpm.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/python.html b/rpm/python.html
index 5a2ec8b62..587639b55 100644
--- a/rpm/python.html
+++ b/rpm/python.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1147,7 +1147,7 @@ <h3>rpm.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rpm/ruby.html b/rpm/ruby.html
index c92a33401..6bd3c18e5 100644
--- a/rpm/ruby.html
+++ b/rpm/ruby.html
@@ -105,10 +105,10 @@ <h1>RPM package file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This parser is for the RPM version 3 file format which is the current version
-of the file format used by RPM 2.1 and later (including RPM version 4.x, which
-is the current version of the RPM tool). There are historical versions of the
-RPM file format, as well as a currently abandoned fork (rpm5). These formats
+                <p><p>This parser is for the RPM version 3 file format which is the current version<br />
+of the file format used by RPM 2.1 and later (including RPM version 4.x, which<br />
+is the current version of the RPM tool). There are historical versions of the<br />
+RPM file format, as well as a currently abandoned fork (rpm5). These formats<br />
 are not covered by this specification.</p>
 </p>
             </div>
@@ -1157,7 +1157,7 @@ <h3>rpm.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/cpp_stl_11.html b/rtcp_payload/cpp_stl_11.html
index f507f052a..8b8cb5a4f 100644
--- a/rtcp_payload/cpp_stl_11.html
+++ b/rtcp_payload/cpp_stl_11.html
@@ -1566,7 +1566,7 @@ <h3>rtcp_payload.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/cpp_stl_98.html b/rtcp_payload/cpp_stl_98.html
index 491a4dc9f..256567580 100644
--- a/rtcp_payload/cpp_stl_98.html
+++ b/rtcp_payload/cpp_stl_98.html
@@ -1709,7 +1709,7 @@ <h3>rtcp_payload.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/csharp.html b/rtcp_payload/csharp.html
index aa8fd7975..5bc9274d5 100644
--- a/rtcp_payload/csharp.html
+++ b/rtcp_payload/csharp.html
@@ -1110,7 +1110,7 @@ <h3>RtcpPayload.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/go.html b/rtcp_payload/go.html
index 58c4b7b0c..f5e3a30fc 100644
--- a/rtcp_payload/go.html
+++ b/rtcp_payload/go.html
@@ -1232,7 +1232,7 @@ <h3>rtcp_payload.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/graphviz.html b/rtcp_payload/graphviz.html
index a0a689587..496be05ba 100644
--- a/rtcp_payload/graphviz.html
+++ b/rtcp_payload/graphviz.html
@@ -553,7 +553,7 @@ <h3>rtcp_payload.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/index.html b/rtcp_payload/index.html
index 67657ebff..1ac606c53 100644
--- a/rtcp_payload/index.html
+++ b/rtcp_payload/index.html
@@ -529,7 +529,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/java.html b/rtcp_payload/java.html
index 5a4856bf8..a14eee677 100644
--- a/rtcp_payload/java.html
+++ b/rtcp_payload/java.html
@@ -1160,7 +1160,7 @@ <h3>RtcpPayload.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/javascript.html b/rtcp_payload/javascript.html
index 131aec393..cc7e8b746 100644
--- a/rtcp_payload/javascript.html
+++ b/rtcp_payload/javascript.html
@@ -849,7 +849,7 @@ <h3>RtcpPayload.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/lua.html b/rtcp_payload/lua.html
index 0c9eff415..d1ea3be69 100644
--- a/rtcp_payload/lua.html
+++ b/rtcp_payload/lua.html
@@ -763,7 +763,7 @@ <h3>rtcp_payload.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/nim.html b/rtcp_payload/nim.html
index ba84358e7..7edb46197 100644
--- a/rtcp_payload/nim.html
+++ b/rtcp_payload/nim.html
@@ -897,7 +897,7 @@ <h3>rtcp_payload.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/perl.html b/rtcp_payload/perl.html
index 7cb8f0598..142ab642a 100644
--- a/rtcp_payload/perl.html
+++ b/rtcp_payload/perl.html
@@ -1254,7 +1254,7 @@ <h3>RtcpPayload.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/php.html b/rtcp_payload/php.html
index c02019a82..de56ef638 100644
--- a/rtcp_payload/php.html
+++ b/rtcp_payload/php.html
@@ -838,7 +838,7 @@ <h3>RtcpPayload.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/python.html b/rtcp_payload/python.html
index a49d4cbaf..4daf0299c 100644
--- a/rtcp_payload/python.html
+++ b/rtcp_payload/python.html
@@ -734,7 +734,7 @@ <h3>rtcp_payload.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtcp_payload/ruby.html b/rtcp_payload/ruby.html
index d3e912e42..6d36d7a9d 100644
--- a/rtcp_payload/ruby.html
+++ b/rtcp_payload/ruby.html
@@ -761,7 +761,7 @@ <h3>rtcp_payload.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/cpp_stl_11.html b/rtp_packet/cpp_stl_11.html
index 71e851ca9..d02c3dd4b 100644
--- a/rtp_packet/cpp_stl_11.html
+++ b/rtp_packet/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -624,7 +624,7 @@ <h3>rtp_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/cpp_stl_98.html b/rtp_packet/cpp_stl_98.html
index 142029ed4..9372ca189 100644
--- a/rtp_packet/cpp_stl_98.html
+++ b/rtp_packet/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -641,7 +641,7 @@ <h3>rtp_packet.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/csharp.html b/rtp_packet/csharp.html
index 0798a211d..74f3937e3 100644
--- a/rtp_packet/csharp.html
+++ b/rtp_packet/csharp.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -505,7 +505,7 @@ <h3>RtpPacket.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/go.html b/rtp_packet/go.html
index 8fe674be7..c9c340898 100644
--- a/rtp_packet/go.html
+++ b/rtp_packet/go.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -534,7 +534,7 @@ <h3>rtp_packet.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/graphviz.html b/rtp_packet/graphviz.html
index 17ede73d7..f104f9111 100644
--- a/rtp_packet/graphviz.html
+++ b/rtp_packet/graphviz.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -321,7 +321,7 @@ <h3>rtp_packet.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/index.html b/rtp_packet/index.html
index 8136773c7..3e3a39434 100644
--- a/rtp_packet/index.html
+++ b/rtp_packet/index.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -362,7 +362,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/java.html b/rtp_packet/java.html
index cf00c5765..a15705dfe 100644
--- a/rtp_packet/java.html
+++ b/rtp_packet/java.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -515,7 +515,7 @@ <h3>RtpPacket.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/javascript.html b/rtp_packet/javascript.html
index 8ff2471c0..5c9d3d87a 100644
--- a/rtp_packet/javascript.html
+++ b/rtp_packet/javascript.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -489,7 +489,7 @@ <h3>RtpPacket.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/lua.html b/rtp_packet/lua.html
index 53484a5cb..1e90db9b0 100644
--- a/rtp_packet/lua.html
+++ b/rtp_packet/lua.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -400,7 +400,7 @@ <h3>rtp_packet.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/nim.html b/rtp_packet/nim.html
index 19d423e45..b5a315feb 100644
--- a/rtp_packet/nim.html
+++ b/rtp_packet/nim.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -439,7 +439,7 @@ <h3>rtp_packet.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/perl.html b/rtp_packet/perl.html
index 80493fa44..9a7311839 100644
--- a/rtp_packet/perl.html
+++ b/rtp_packet/perl.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -488,7 +488,7 @@ <h3>RtpPacket.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/php.html b/rtp_packet/php.html
index 5f6807c67..bc01616cc 100644
--- a/rtp_packet/php.html
+++ b/rtp_packet/php.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -425,7 +425,7 @@ <h3>RtpPacket.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/python.html b/rtp_packet/python.html
index 86d14530b..26431634a 100644
--- a/rtp_packet/python.html
+++ b/rtp_packet/python.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -433,7 +433,7 @@ <h3>rtp_packet.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtp_packet/ruby.html b/rtp_packet/ruby.html
index b032aa868..7c176e89b 100644
--- a/rtp_packet/ruby.html
+++ b/rtp_packet/ruby.html
@@ -105,9 +105,9 @@ <h1>RTP (Real-time Transport Protocol):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The Real-time Transport Protocol (RTP) is a widely used network
-protocol for transmitting audio or video. It usually works with the
-RTP Control Protocol (RTCP). The transmission can be based on
+                <p><p>The Real-time Transport Protocol (RTP) is a widely used network<br />
+protocol for transmitting audio or video. It usually works with the<br />
+RTP Control Protocol (RTCP). The transmission can be based on<br />
 Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h3>rtp_packet.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/cpp_stl_11.html b/rtpdump/cpp_stl_11.html
index 7afc5cb44..3772ed459 100644
--- a/rtpdump/cpp_stl_11.html
+++ b/rtpdump/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -589,7 +589,7 @@ <h3>rtpdump.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/cpp_stl_98.html b/rtpdump/cpp_stl_98.html
index 723e11750..272300177 100644
--- a/rtpdump/cpp_stl_98.html
+++ b/rtpdump/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -624,7 +624,7 @@ <h3>rtpdump.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/csharp.html b/rtpdump/csharp.html
index 091d22ab4..22b0e11a0 100644
--- a/rtpdump/csharp.html
+++ b/rtpdump/csharp.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -470,7 +470,7 @@ <h3>Rtpdump.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/go.html b/rtpdump/go.html
index d35c9db58..5859e0bb8 100644
--- a/rtpdump/go.html
+++ b/rtpdump/go.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -468,7 +468,7 @@ <h3>rtpdump.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/graphviz.html b/rtpdump/graphviz.html
index 16e17f7ac..cfec42982 100644
--- a/rtpdump/graphviz.html
+++ b/rtpdump/graphviz.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -302,7 +302,7 @@ <h3>rtpdump.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/index.html b/rtpdump/index.html
index f145310dc..f0ea32336 100644
--- a/rtpdump/index.html
+++ b/rtpdump/index.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -313,7 +313,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/java.html b/rtpdump/java.html
index c3212a199..903aa56d6 100644
--- a/rtpdump/java.html
+++ b/rtpdump/java.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -486,7 +486,7 @@ <h3>Rtpdump.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/javascript.html b/rtpdump/javascript.html
index 277bd8099..5e0a4b875 100644
--- a/rtpdump/javascript.html
+++ b/rtpdump/javascript.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -413,7 +413,7 @@ <h3>Rtpdump.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/lua.html b/rtpdump/lua.html
index b1fea3452..e6669b056 100644
--- a/rtpdump/lua.html
+++ b/rtpdump/lua.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -350,7 +350,7 @@ <h3>rtpdump.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/nim.html b/rtpdump/nim.html
index 293b44de1..b303fca57 100644
--- a/rtpdump/nim.html
+++ b/rtpdump/nim.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -407,7 +407,7 @@ <h3>rtpdump.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/perl.html b/rtpdump/perl.html
index e20c380a0..b629acf0c 100644
--- a/rtpdump/perl.html
+++ b/rtpdump/perl.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -459,7 +459,7 @@ <h3>Rtpdump.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/php.html b/rtpdump/php.html
index 87030f215..9da63d54c 100644
--- a/rtpdump/php.html
+++ b/rtpdump/php.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -389,7 +389,7 @@ <h3>Rtpdump.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/python.html b/rtpdump/python.html
index 7c4e9abc1..66374add8 100644
--- a/rtpdump/python.html
+++ b/rtpdump/python.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -367,7 +367,7 @@ <h3>rtpdump.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/rtpdump/ruby.html b/rtpdump/ruby.html
index b56468e44..320a1bd20 100644
--- a/rtpdump/ruby.html
+++ b/rtpdump/ruby.html
@@ -105,7 +105,7 @@ <h1>Rtpdump (rtptools):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>rtpdump is a format used by rtptools to record and replay
+                <p><p>rtpdump is a format used by rtptools to record and replay<br />
 rtp data from network capture.</p>
 </p>
             </div>
@@ -403,7 +403,7 @@ <h3>rtpdump.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/cpp_stl_11.html b/ruby_marshal/cpp_stl_11.html
index 23cba4ad9..82c882786 100644
--- a/ruby_marshal/cpp_stl_11.html
+++ b/ruby_marshal/cpp_stl_11.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -1202,7 +1202,7 @@ <h3>ruby_marshal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/cpp_stl_98.html b/ruby_marshal/cpp_stl_98.html
index 08cc97828..86c1e3426 100644
--- a/ruby_marshal/cpp_stl_98.html
+++ b/ruby_marshal/cpp_stl_98.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -1333,7 +1333,7 @@ <h3>ruby_marshal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/csharp.html b/ruby_marshal/csharp.html
index e5eca319b..3ac8d0c14 100644
--- a/ruby_marshal/csharp.html
+++ b/ruby_marshal/csharp.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -882,7 +882,7 @@ <h3>RubyMarshal.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/go.html b/ruby_marshal/go.html
index 8763610dd..edaf3ee26 100644
--- a/ruby_marshal/go.html
+++ b/ruby_marshal/go.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -989,7 +989,7 @@ <h3>ruby_marshal.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/graphviz.html b/ruby_marshal/graphviz.html
index 540148a96..1112d2ab7 100644
--- a/ruby_marshal/graphviz.html
+++ b/ruby_marshal/graphviz.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -470,7 +470,7 @@ <h3>ruby_marshal.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/index.html b/ruby_marshal/index.html
index 3da71d0b3..0e455bcef 100644
--- a/ruby_marshal/index.html
+++ b/ruby_marshal/index.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/java.html b/ruby_marshal/java.html
index 2f8595473..ea3fc085b 100644
--- a/ruby_marshal/java.html
+++ b/ruby_marshal/java.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -937,7 +937,7 @@ <h3>RubyMarshal.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/javascript.html b/ruby_marshal/javascript.html
index 5b6c38c9a..0df167c99 100644
--- a/ruby_marshal/javascript.html
+++ b/ruby_marshal/javascript.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -727,7 +727,7 @@ <h3>RubyMarshal.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/lua.html b/ruby_marshal/lua.html
index 31ea49bd8..4d38ddf5c 100644
--- a/ruby_marshal/lua.html
+++ b/ruby_marshal/lua.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -613,7 +613,7 @@ <h3>ruby_marshal.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/nim.html b/ruby_marshal/nim.html
index a487d10c7..83cad7d5c 100644
--- a/ruby_marshal/nim.html
+++ b/ruby_marshal/nim.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -725,7 +725,7 @@ <h3>ruby_marshal.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/perl.html b/ruby_marshal/perl.html
index 387f4c7d5..8c2e9f711 100644
--- a/ruby_marshal/perl.html
+++ b/ruby_marshal/perl.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -884,7 +884,7 @@ <h3>RubyMarshal.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/php.html b/ruby_marshal/php.html
index 10e37d074..6330e91a7 100644
--- a/ruby_marshal/php.html
+++ b/ruby_marshal/php.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -672,7 +672,7 @@ <h3>RubyMarshal.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/python.html b/ruby_marshal/python.html
index c3b335bed..d16409f3a 100644
--- a/ruby_marshal/python.html
+++ b/ruby_marshal/python.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -617,7 +617,7 @@ <h3>ruby_marshal.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ruby_marshal/ruby.html b/ruby_marshal/ruby.html
index 002b33564..d18a319de 100644
--- a/ruby_marshal/ruby.html
+++ b/ruby_marshal/ruby.html
@@ -105,24 +105,24 @@ <h1>ruby_marshal:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Ruby's Marshal module allows serialization and deserialization of
-many standard and arbitrary Ruby objects in a compact binary
-format. It is relatively fast, available in stdlibs standard and
-allows conservation of language-specific properties (such as symbols
+                <p><p>Ruby's Marshal module allows serialization and deserialization of<br />
+many standard and arbitrary Ruby objects in a compact binary<br />
+format. It is relatively fast, available in stdlibs standard and<br />
+allows conservation of language-specific properties (such as symbols<br />
 or encoding-aware strings).</p>
-<p>Feature-wise, it is comparable to other language-specific
+<p>Feature-wise, it is comparable to other language-specific<br />
 implementations, such as:</p>
 <ul>
-<li>Java's
+<li>Java's<br />
 <a href="https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html">Serializable</a></li>
-<li>.NET
+<li>.NET<br />
 <a href="https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-7.0">BinaryFormatter</a></li>
-<li>Python's
-<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,
-<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and
+<li>Python's<br />
+<a href="https://docs.python.org/3/library/marshal.html">marshal</a>,<br />
+<a href="https://docs.python.org/3/library/pickle.html">pickle</a> and<br />
 <a href="https://docs.python.org/3/library/shelve.html">shelve</a></li>
 </ul>
-<p>From internal perspective, serialized stream consists of a simple
+<p>From internal perspective, serialized stream consists of a simple<br />
 magic header and a record.</p>
 </p>
             </div>
@@ -652,7 +652,7 @@ <h3>ruby_marshal.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/cpp_stl_11.html b/s3m/cpp_stl_11.html
index 68fb03950..6f7bf6c04 100644
--- a/s3m/cpp_stl_11.html
+++ b/s3m/cpp_stl_11.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -1349,7 +1349,7 @@ <h3>s3m.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/cpp_stl_98.html b/s3m/cpp_stl_98.html
index e05e97679..3af298bd2 100644
--- a/s3m/cpp_stl_98.html
+++ b/s3m/cpp_stl_98.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -1471,7 +1471,7 @@ <h3>s3m.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/csharp.html b/s3m/csharp.html
index 6ea3b32c2..797345428 100644
--- a/s3m/csharp.html
+++ b/s3m/csharp.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -993,7 +993,7 @@ <h3>S3m.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/go.html b/s3m/go.html
index c5f3e3024..6dc870ec2 100644
--- a/s3m/go.html
+++ b/s3m/go.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -1146,7 +1146,7 @@ <h3>s3m.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/graphviz.html b/s3m/graphviz.html
index 54194e935..dea444423 100644
--- a/s3m/graphviz.html
+++ b/s3m/graphviz.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -504,7 +504,7 @@ <h3>s3m.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/index.html b/s3m/index.html
index 1a3a4ec05..8781abcfb 100644
--- a/s3m/index.html
+++ b/s3m/index.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -541,7 +541,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/java.html b/s3m/java.html
index e0f9cdc68..9c3a54247 100644
--- a/s3m/java.html
+++ b/s3m/java.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -1038,7 +1038,7 @@ <h3>S3m.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/javascript.html b/s3m/javascript.html
index f330aa427..238126cc3 100644
--- a/s3m/javascript.html
+++ b/s3m/javascript.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -750,7 +750,7 @@ <h3>S3m.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/lua.html b/s3m/lua.html
index 1546ddf1e..e7fab0e3a 100644
--- a/s3m/lua.html
+++ b/s3m/lua.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -668,7 +668,7 @@ <h3>s3m.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/nim.html b/s3m/nim.html
index 247076aa8..ee9c7ccd9 100644
--- a/s3m/nim.html
+++ b/s3m/nim.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -823,7 +823,7 @@ <h3>s3m.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/perl.html b/s3m/perl.html
index 87c9d27aa..8c4b3a413 100644
--- a/s3m/perl.html
+++ b/s3m/perl.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -1157,7 +1157,7 @@ <h3>S3m.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/php.html b/s3m/php.html
index 97dcc901f..5e5df0e19 100644
--- a/s3m/php.html
+++ b/s3m/php.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -800,7 +800,7 @@ <h3>S3m.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/python.html b/s3m/python.html
index 2c815ca41..1d0132e39 100644
--- a/s3m/python.html
+++ b/s3m/python.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -640,7 +640,7 @@ <h3>s3m.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/s3m/ruby.html b/s3m/ruby.html
index ee3298d50..ba253f300 100644
--- a/s3m/ruby.html
+++ b/s3m/ruby.html
@@ -105,19 +105,19 @@ <h1>Scream Tracker 3 module:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Scream Tracker 3 module is a tracker music file format that, as all
-tracker music, bundles both sound samples and instructions on which
-notes to play. It originates from a Scream Tracker 3 music editor
-(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)
+                <p><p>Scream Tracker 3 module is a tracker music file format that, as all<br />
+tracker music, bundles both sound samples and instructions on which<br />
+notes to play. It originates from a Scream Tracker 3 music editor<br />
+(1994) by Future Crew, derived from original Scream Tracker 2 (.stm)<br />
 module format.</p>
-<p>Instrument descriptions in S3M format allow to use either digital
+<p>Instrument descriptions in S3M format allow to use either digital<br />
 samples or setup and control AdLib (OPL2) synth.</p>
-<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally
-a 64-row long table, which instructs which notes to play on which
-time measure. &quot;Patterns&quot; are played one-by-one in a sequence
+<p>Music is organized in so called <code>patterns</code>. &quot;Pattern&quot; is a generally<br />
+a 64-row long table, which instructs which notes to play on which<br />
+time measure. &quot;Patterns&quot; are played one-by-one in a sequence<br />
 determined by <code>orders</code>, which is essentially an array of pattern IDs</p>
 <ul>
-<li>this way it's possible to reuse certain patterns more than once
+<li>this way it's possible to reuse certain patterns more than once<br />
 for repetitive musical phrases.</li>
 </ul>
 </p>
@@ -725,7 +725,7 @@ <h3>s3m.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/cpp_stl_11.html b/saints_row_2_vpp_pc/cpp_stl_11.html
index c249558ea..ccf7218f3 100644
--- a/saints_row_2_vpp_pc/cpp_stl_11.html
+++ b/saints_row_2_vpp_pc/cpp_stl_11.html
@@ -801,7 +801,7 @@ <h3>saints_row_2_vpp_pc.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/cpp_stl_98.html b/saints_row_2_vpp_pc/cpp_stl_98.html
index 2483bfc60..371e14902 100644
--- a/saints_row_2_vpp_pc/cpp_stl_98.html
+++ b/saints_row_2_vpp_pc/cpp_stl_98.html
@@ -854,7 +854,7 @@ <h3>saints_row_2_vpp_pc.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/csharp.html b/saints_row_2_vpp_pc/csharp.html
index ff03c9bd4..64c2ceb27 100644
--- a/saints_row_2_vpp_pc/csharp.html
+++ b/saints_row_2_vpp_pc/csharp.html
@@ -625,7 +625,7 @@ <h3>SaintsRow2VppPc.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/go.html b/saints_row_2_vpp_pc/go.html
index e99f8afe1..f03dd8c83 100644
--- a/saints_row_2_vpp_pc/go.html
+++ b/saints_row_2_vpp_pc/go.html
@@ -729,7 +729,7 @@ <h3>saints_row_2_vpp_pc.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/graphviz.html b/saints_row_2_vpp_pc/graphviz.html
index 146887c70..a9d6fd219 100644
--- a/saints_row_2_vpp_pc/graphviz.html
+++ b/saints_row_2_vpp_pc/graphviz.html
@@ -366,7 +366,7 @@ <h3>saints_row_2_vpp_pc.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/index.html b/saints_row_2_vpp_pc/index.html
index 77f118e13..5e4b48aeb 100644
--- a/saints_row_2_vpp_pc/index.html
+++ b/saints_row_2_vpp_pc/index.html
@@ -331,7 +331,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/java.html b/saints_row_2_vpp_pc/java.html
index 30e8978ba..de74d7fb2 100644
--- a/saints_row_2_vpp_pc/java.html
+++ b/saints_row_2_vpp_pc/java.html
@@ -589,7 +589,7 @@ <h3>SaintsRow2VppPc.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/javascript.html b/saints_row_2_vpp_pc/javascript.html
index d10a2c5a4..98cf17cb5 100644
--- a/saints_row_2_vpp_pc/javascript.html
+++ b/saints_row_2_vpp_pc/javascript.html
@@ -492,7 +492,7 @@ <h3>SaintsRow2VppPc.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/lua.html b/saints_row_2_vpp_pc/lua.html
index 5465a464f..ba0cdba5e 100644
--- a/saints_row_2_vpp_pc/lua.html
+++ b/saints_row_2_vpp_pc/lua.html
@@ -462,7 +462,7 @@ <h3>saints_row_2_vpp_pc.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/nim.html b/saints_row_2_vpp_pc/nim.html
index a5fb5d824..6c10228ed 100644
--- a/saints_row_2_vpp_pc/nim.html
+++ b/saints_row_2_vpp_pc/nim.html
@@ -521,7 +521,7 @@ <h3>saints_row_2_vpp_pc.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/perl.html b/saints_row_2_vpp_pc/perl.html
index 08329ddb4..f115437e3 100644
--- a/saints_row_2_vpp_pc/perl.html
+++ b/saints_row_2_vpp_pc/perl.html
@@ -625,7 +625,7 @@ <h3>SaintsRow2VppPc.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/php.html b/saints_row_2_vpp_pc/php.html
index 7a95a7e33..96f55f19c 100644
--- a/saints_row_2_vpp_pc/php.html
+++ b/saints_row_2_vpp_pc/php.html
@@ -474,7 +474,7 @@ <h3>SaintsRow2VppPc.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/python.html b/saints_row_2_vpp_pc/python.html
index 90a756506..6380ee3af 100644
--- a/saints_row_2_vpp_pc/python.html
+++ b/saints_row_2_vpp_pc/python.html
@@ -475,7 +475,7 @@ <h3>saints_row_2_vpp_pc.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/saints_row_2_vpp_pc/ruby.html b/saints_row_2_vpp_pc/ruby.html
index 1b5771ea7..8dba7a046 100644
--- a/saints_row_2_vpp_pc/ruby.html
+++ b/saints_row_2_vpp_pc/ruby.html
@@ -470,7 +470,7 @@ <h3>saints_row_2_vpp_pc.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/cpp_stl_11.html b/shapefile_index/cpp_stl_11.html
index 9f97de108..e8f2aadd5 100644
--- a/shapefile_index/cpp_stl_11.html
+++ b/shapefile_index/cpp_stl_11.html
@@ -705,7 +705,7 @@ <h3>shapefile_index.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/cpp_stl_98.html b/shapefile_index/cpp_stl_98.html
index b6f1790f4..82a4c6041 100644
--- a/shapefile_index/cpp_stl_98.html
+++ b/shapefile_index/cpp_stl_98.html
@@ -761,7 +761,7 @@ <h3>shapefile_index.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/csharp.html b/shapefile_index/csharp.html
index bd3400b65..c2986decb 100644
--- a/shapefile_index/csharp.html
+++ b/shapefile_index/csharp.html
@@ -555,7 +555,7 @@ <h3>ShapefileIndex.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/go.html b/shapefile_index/go.html
index bfd44e79c..8a3d0c761 100644
--- a/shapefile_index/go.html
+++ b/shapefile_index/go.html
@@ -562,7 +562,7 @@ <h3>shapefile_index.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/graphviz.html b/shapefile_index/graphviz.html
index c618a7774..f28799bc5 100644
--- a/shapefile_index/graphviz.html
+++ b/shapefile_index/graphviz.html
@@ -348,7 +348,7 @@ <h3>shapefile_index.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/index.html b/shapefile_index/index.html
index 8da90fe41..e0f3378ab 100644
--- a/shapefile_index/index.html
+++ b/shapefile_index/index.html
@@ -345,7 +345,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/java.html b/shapefile_index/java.html
index 7a824685c..f48d437c0 100644
--- a/shapefile_index/java.html
+++ b/shapefile_index/java.html
@@ -588,7 +588,7 @@ <h3>ShapefileIndex.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/javascript.html b/shapefile_index/javascript.html
index 2f5faa459..4118a396d 100644
--- a/shapefile_index/javascript.html
+++ b/shapefile_index/javascript.html
@@ -487,7 +487,7 @@ <h3>ShapefileIndex.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/lua.html b/shapefile_index/lua.html
index 9d98d69a9..50c231847 100644
--- a/shapefile_index/lua.html
+++ b/shapefile_index/lua.html
@@ -416,7 +416,7 @@ <h3>shapefile_index.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/nim.html b/shapefile_index/nim.html
index be5064bda..07b6b51bb 100644
--- a/shapefile_index/nim.html
+++ b/shapefile_index/nim.html
@@ -448,7 +448,7 @@ <h3>shapefile_index.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/perl.html b/shapefile_index/perl.html
index aeee14d35..ead62575f 100644
--- a/shapefile_index/perl.html
+++ b/shapefile_index/perl.html
@@ -581,7 +581,7 @@ <h3>ShapefileIndex.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/php.html b/shapefile_index/php.html
index 923a99ca5..5aa395296 100644
--- a/shapefile_index/php.html
+++ b/shapefile_index/php.html
@@ -455,7 +455,7 @@ <h3>ShapefileIndex.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/python.html b/shapefile_index/python.html
index 6a2c7a41d..ed7a4e41b 100644
--- a/shapefile_index/python.html
+++ b/shapefile_index/python.html
@@ -432,7 +432,7 @@ <h3>shapefile_index.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_index/ruby.html b/shapefile_index/ruby.html
index 57c79efa8..48b1d1aac 100644
--- a/shapefile_index/ruby.html
+++ b/shapefile_index/ruby.html
@@ -455,7 +455,7 @@ <h3>shapefile_index.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/cpp_stl_11.html b/shapefile_main/cpp_stl_11.html
index 94d43a198..581968f31 100644
--- a/shapefile_main/cpp_stl_11.html
+++ b/shapefile_main/cpp_stl_11.html
@@ -1837,7 +1837,7 @@ <h3>shapefile_main.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/cpp_stl_98.html b/shapefile_main/cpp_stl_98.html
index 81fe5a731..64045a607 100644
--- a/shapefile_main/cpp_stl_98.html
+++ b/shapefile_main/cpp_stl_98.html
@@ -2184,7 +2184,7 @@ <h3>shapefile_main.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/csharp.html b/shapefile_main/csharp.html
index 39a78357c..ed2159893 100644
--- a/shapefile_main/csharp.html
+++ b/shapefile_main/csharp.html
@@ -1322,7 +1322,7 @@ <h3>ShapefileMain.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/go.html b/shapefile_main/go.html
index e282fc9e1..4bfdf4592 100644
--- a/shapefile_main/go.html
+++ b/shapefile_main/go.html
@@ -1552,7 +1552,7 @@ <h3>shapefile_main.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/graphviz.html b/shapefile_main/graphviz.html
index fc7e71eb4..322a6e29c 100644
--- a/shapefile_main/graphviz.html
+++ b/shapefile_main/graphviz.html
@@ -682,7 +682,7 @@ <h3>shapefile_main.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/index.html b/shapefile_main/index.html
index 4c1090a69..da4956608 100644
--- a/shapefile_main/index.html
+++ b/shapefile_main/index.html
@@ -625,7 +625,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/java.html b/shapefile_main/java.html
index 2d863efdd..e6217d37c 100644
--- a/shapefile_main/java.html
+++ b/shapefile_main/java.html
@@ -1420,7 +1420,7 @@ <h3>ShapefileMain.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/javascript.html b/shapefile_main/javascript.html
index 44762bc2b..313f46e7f 100644
--- a/shapefile_main/javascript.html
+++ b/shapefile_main/javascript.html
@@ -942,7 +942,7 @@ <h3>ShapefileMain.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/lua.html b/shapefile_main/lua.html
index 4aeecf45a..6da18a0a0 100644
--- a/shapefile_main/lua.html
+++ b/shapefile_main/lua.html
@@ -833,7 +833,7 @@ <h3>shapefile_main.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/nim.html b/shapefile_main/nim.html
index 29d2b86b1..990f0dfc6 100644
--- a/shapefile_main/nim.html
+++ b/shapefile_main/nim.html
@@ -1014,7 +1014,7 @@ <h3>shapefile_main.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/perl.html b/shapefile_main/perl.html
index 6be40a303..edcd34a99 100644
--- a/shapefile_main/perl.html
+++ b/shapefile_main/perl.html
@@ -1749,7 +1749,7 @@ <h3>ShapefileMain.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/php.html b/shapefile_main/php.html
index c8304ba94..b3d5a2898 100644
--- a/shapefile_main/php.html
+++ b/shapefile_main/php.html
@@ -1066,7 +1066,7 @@ <h3>ShapefileMain.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/python.html b/shapefile_main/python.html
index 30e130c24..4ba285684 100644
--- a/shapefile_main/python.html
+++ b/shapefile_main/python.html
@@ -796,7 +796,7 @@ <h3>shapefile_main.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/shapefile_main/ruby.html b/shapefile_main/ruby.html
index 5d1716d33..cdaa261f0 100644
--- a/shapefile_main/ruby.html
+++ b/shapefile_main/ruby.html
@@ -908,7 +908,7 @@ <h3>shapefile_main.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/cpp_stl_11.html b/some_ip/cpp_stl_11.html
index cea386da9..edd30f281 100644
--- a/some_ip/cpp_stl_11.html
+++ b/some_ip/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -806,7 +806,7 @@ <h3>some_ip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/cpp_stl_98.html b/some_ip/cpp_stl_98.html
index 8fd46e4ef..22f56caba 100644
--- a/some_ip/cpp_stl_98.html
+++ b/some_ip/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -853,7 +853,7 @@ <h3>some_ip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/csharp.html b/some_ip/csharp.html
index cfde466ec..d5afca96d 100644
--- a/some_ip/csharp.html
+++ b/some_ip/csharp.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -639,7 +639,7 @@ <h3>SomeIp.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/go.html b/some_ip/go.html
index 0b5770672..34934f8d0 100644
--- a/some_ip/go.html
+++ b/some_ip/go.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -652,7 +652,7 @@ <h3>some_ip.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/graphviz.html b/some_ip/graphviz.html
index c214272d1..e54f8fc68 100644
--- a/some_ip/graphviz.html
+++ b/some_ip/graphviz.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -330,7 +330,7 @@ <h3>some_ip.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/index.html b/some_ip/index.html
index fcee1eec9..8fe7bba37 100644
--- a/some_ip/index.html
+++ b/some_ip/index.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -392,7 +392,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/java.html b/some_ip/java.html
index 8eb600cfc..86f9dadc0 100644
--- a/some_ip/java.html
+++ b/some_ip/java.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -645,7 +645,7 @@ <h3>SomeIp.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/javascript.html b/some_ip/javascript.html
index a54d551f4..57b525278 100644
--- a/some_ip/javascript.html
+++ b/some_ip/javascript.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -562,7 +562,7 @@ <h3>SomeIp.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/lua.html b/some_ip/lua.html
index afdc5ca3b..a291047b2 100644
--- a/some_ip/lua.html
+++ b/some_ip/lua.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -462,7 +462,7 @@ <h3>some_ip.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/nim.html b/some_ip/nim.html
index 735d2cae7..835cd40ad 100644
--- a/some_ip/nim.html
+++ b/some_ip/nim.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -548,7 +548,7 @@ <h3>some_ip.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/perl.html b/some_ip/perl.html
index 6f3eff780..6f765cc42 100644
--- a/some_ip/perl.html
+++ b/some_ip/perl.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -559,7 +559,7 @@ <h3>SomeIp.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/php.html b/some_ip/php.html
index 9e719d085..63e451a07 100644
--- a/some_ip/php.html
+++ b/some_ip/php.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -511,7 +511,7 @@ <h3>SomeIp.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/python.html b/some_ip/python.html
index d52cfe387..4ef31ca53 100644
--- a/some_ip/python.html
+++ b/some_ip/python.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -458,7 +458,7 @@ <h3>some_ip.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip/ruby.html b/some_ip/ruby.html
index 9c19d0c23..ef2f2d8ba 100644
--- a/some_ip/ruby.html
+++ b/some_ip/ruby.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded
-communication protocol which supports remoteprocedure calls, event notifications
+                <p><p>SOME/IP (Scalable service-Oriented MiddlewarE over IP) is an automotive/embedded<br />
+communication protocol which supports remoteprocedure calls, event notifications<br />
 and the underlying serialization/wire format.</p>
 </p>
             </div>
@@ -514,7 +514,7 @@ <h3>some_ip.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/cpp_stl_11.html b/some_ip_container/cpp_stl_11.html
index facb732f3..243bd6dcd 100644
--- a/some_ip_container/cpp_stl_11.html
+++ b/some_ip_container/cpp_stl_11.html
@@ -410,7 +410,7 @@ <h3>some_ip_container.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/cpp_stl_98.html b/some_ip_container/cpp_stl_98.html
index 3bf560268..86e1017fb 100644
--- a/some_ip_container/cpp_stl_98.html
+++ b/some_ip_container/cpp_stl_98.html
@@ -424,7 +424,7 @@ <h3>some_ip_container.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/csharp.html b/some_ip_container/csharp.html
index d184009d5..53d18f6ae 100644
--- a/some_ip_container/csharp.html
+++ b/some_ip_container/csharp.html
@@ -329,7 +329,7 @@ <h3>SomeIpContainer.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/go.html b/some_ip_container/go.html
index 222b989b4..adffae304 100644
--- a/some_ip_container/go.html
+++ b/some_ip_container/go.html
@@ -286,7 +286,7 @@ <h3>some_ip_container.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/graphviz.html b/some_ip_container/graphviz.html
index 1d9e00259..6da6b9e9b 100644
--- a/some_ip_container/graphviz.html
+++ b/some_ip_container/graphviz.html
@@ -264,7 +264,7 @@ <h3>some_ip_container.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/index.html b/some_ip_container/index.html
index ca8701d3d..f3e902762 100644
--- a/some_ip_container/index.html
+++ b/some_ip_container/index.html
@@ -249,7 +249,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/java.html b/some_ip_container/java.html
index cbd90a6a2..f05fd6fad 100644
--- a/some_ip_container/java.html
+++ b/some_ip_container/java.html
@@ -337,7 +337,7 @@ <h3>SomeIpContainer.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/javascript.html b/some_ip_container/javascript.html
index 2e4182f1b..2d143b4d4 100644
--- a/some_ip_container/javascript.html
+++ b/some_ip_container/javascript.html
@@ -320,7 +320,7 @@ <h3>SomeIpContainer.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/lua.html b/some_ip_container/lua.html
index 880107c6e..9df37219f 100644
--- a/some_ip_container/lua.html
+++ b/some_ip_container/lua.html
@@ -274,7 +274,7 @@ <h3>some_ip_container.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/nim.html b/some_ip_container/nim.html
index 24f34d0da..324365fdc 100644
--- a/some_ip_container/nim.html
+++ b/some_ip_container/nim.html
@@ -279,7 +279,7 @@ <h3>some_ip_container.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/perl.html b/some_ip_container/perl.html
index 805e0bcf2..9c32b3e5d 100644
--- a/some_ip_container/perl.html
+++ b/some_ip_container/perl.html
@@ -298,7 +298,7 @@ <h3>SomeIpContainer.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/php.html b/some_ip_container/php.html
index 7ec64c7f8..4347cff8f 100644
--- a/some_ip_container/php.html
+++ b/some_ip_container/php.html
@@ -271,7 +271,7 @@ <h3>SomeIpContainer.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/python.html b/some_ip_container/python.html
index 59c6f274e..bbfa42d1d 100644
--- a/some_ip_container/python.html
+++ b/some_ip_container/python.html
@@ -316,7 +316,7 @@ <h3>some_ip_container.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_container/ruby.html b/some_ip_container/ruby.html
index 1954093c0..3681ce65b 100644
--- a/some_ip_container/ruby.html
+++ b/some_ip_container/ruby.html
@@ -316,7 +316,7 @@ <h3>some_ip_container.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/cpp_stl_11.html b/some_ip_sd/cpp_stl_11.html
index 361d5b7a4..dcb17f200 100644
--- a/some_ip_sd/cpp_stl_11.html
+++ b/some_ip_sd/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -510,7 +510,7 @@ <h3>some_ip_sd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/cpp_stl_98.html b/some_ip_sd/cpp_stl_98.html
index 7f4c8e40a..2a68c33b3 100644
--- a/some_ip_sd/cpp_stl_98.html
+++ b/some_ip_sd/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -539,7 +539,7 @@ <h3>some_ip_sd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/csharp.html b/some_ip_sd/csharp.html
index cc8a14327..4a0c5d8bb 100644
--- a/some_ip_sd/csharp.html
+++ b/some_ip_sd/csharp.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -404,7 +404,7 @@ <h3>SomeIpSd.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/go.html b/some_ip_sd/go.html
index c73247bde..2ba3f31fa 100644
--- a/some_ip_sd/go.html
+++ b/some_ip_sd/go.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -394,7 +394,7 @@ <h3>some_ip_sd.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/graphviz.html b/some_ip_sd/graphviz.html
index 5051b21f5..a22bdd2a6 100644
--- a/some_ip_sd/graphviz.html
+++ b/some_ip_sd/graphviz.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -290,7 +290,7 @@ <h3>some_ip_sd.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/index.html b/some_ip_sd/index.html
index 580c070ac..aec621da5 100644
--- a/some_ip_sd/index.html
+++ b/some_ip_sd/index.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -290,7 +290,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/java.html b/some_ip_sd/java.html
index 3df2ec88f..bd1f6a43e 100644
--- a/some_ip_sd/java.html
+++ b/some_ip_sd/java.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -414,7 +414,7 @@ <h3>SomeIpSd.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/javascript.html b/some_ip_sd/javascript.html
index d87a093ce..fc808b2c8 100644
--- a/some_ip_sd/javascript.html
+++ b/some_ip_sd/javascript.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -366,7 +366,7 @@ <h3>SomeIpSd.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/lua.html b/some_ip_sd/lua.html
index ae57575d0..0bb1aa26d 100644
--- a/some_ip_sd/lua.html
+++ b/some_ip_sd/lua.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -315,7 +315,7 @@ <h3>some_ip_sd.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/nim.html b/some_ip_sd/nim.html
index 868c298ee..1834dc27d 100644
--- a/some_ip_sd/nim.html
+++ b/some_ip_sd/nim.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -352,7 +352,7 @@ <h3>some_ip_sd.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/perl.html b/some_ip_sd/perl.html
index 1ad86a48a..573f64d24 100644
--- a/some_ip_sd/perl.html
+++ b/some_ip_sd/perl.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -402,7 +402,7 @@ <h3>SomeIpSd.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/php.html b/some_ip_sd/php.html
index 0784db600..8c36f7cb2 100644
--- a/some_ip_sd/php.html
+++ b/some_ip_sd/php.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -332,7 +332,7 @@ <h3>SomeIpSd.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/python.html b/some_ip_sd/python.html
index d40b557bc..7bef6310a 100644
--- a/some_ip_sd/python.html
+++ b/some_ip_sd/python.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -355,7 +355,7 @@ <h3>some_ip_sd.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd/ruby.html b/some_ip_sd/ruby.html
index 3b18b31db..320ebb180 100644
--- a/some_ip_sd/ruby.html
+++ b/some_ip_sd/ruby.html
@@ -105,11 +105,11 @@ <h1>AUTOSAR SOME/IP Service Discovery:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The main tasks of the Service Discovery Protocol are communicating the
-availability of functional entities called services in the in-vehicle
-communication as well as controlling the send behavior of event messages.
-This allows sending only event messages to receivers requiring them (Publish/Subscribe).
-The solution described here is also known as SOME/IP-SD
+                <p><p>The main tasks of the Service Discovery Protocol are communicating the<br />
+availability of functional entities called services in the in-vehicle<br />
+communication as well as controlling the send behavior of event messages.<br />
+This allows sending only event messages to receivers requiring them (Publish/Subscribe).<br />
+The solution described here is also known as SOME/IP-SD<br />
 (Scalable service-Oriented MiddlewarE over IP - Service Discovery).</p>
 </p>
             </div>
@@ -366,7 +366,7 @@ <h3>some_ip_sd.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/cpp_stl_11.html b/some_ip_sd_entries/cpp_stl_11.html
index 5494dd2f3..02438e984 100644
--- a/some_ip_sd_entries/cpp_stl_11.html
+++ b/some_ip_sd_entries/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -664,7 +664,7 @@ <h3>some_ip_sd_entries.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/cpp_stl_98.html b/some_ip_sd_entries/cpp_stl_98.html
index 41257b6bf..40afd1cb8 100644
--- a/some_ip_sd_entries/cpp_stl_98.html
+++ b/some_ip_sd_entries/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -708,7 +708,7 @@ <h3>some_ip_sd_entries.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/csharp.html b/some_ip_sd_entries/csharp.html
index 2b105555d..fdfbd56b4 100644
--- a/some_ip_sd_entries/csharp.html
+++ b/some_ip_sd_entries/csharp.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -502,7 +502,7 @@ <h3>SomeIpSdEntries.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/go.html b/some_ip_sd_entries/go.html
index 8c091803f..9e8a6ac4e 100644
--- a/some_ip_sd_entries/go.html
+++ b/some_ip_sd_entries/go.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -501,7 +501,7 @@ <h3>some_ip_sd_entries.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/graphviz.html b/some_ip_sd_entries/graphviz.html
index 2d01e6dfe..289280d78 100644
--- a/some_ip_sd_entries/graphviz.html
+++ b/some_ip_sd_entries/graphviz.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -329,7 +329,7 @@ <h3>some_ip_sd_entries.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/index.html b/some_ip_sd_entries/index.html
index d29851ec7..06fcc6918 100644
--- a/some_ip_sd_entries/index.html
+++ b/some_ip_sd_entries/index.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -318,7 +318,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/java.html b/some_ip_sd_entries/java.html
index 760509187..e1473f10e 100644
--- a/some_ip_sd_entries/java.html
+++ b/some_ip_sd_entries/java.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -544,7 +544,7 @@ <h3>SomeIpSdEntries.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/javascript.html b/some_ip_sd_entries/javascript.html
index 907e57ea2..423b6d4bf 100644
--- a/some_ip_sd_entries/javascript.html
+++ b/some_ip_sd_entries/javascript.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -429,7 +429,7 @@ <h3>SomeIpSdEntries.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/lua.html b/some_ip_sd_entries/lua.html
index 7abf450a4..45545f9d0 100644
--- a/some_ip_sd_entries/lua.html
+++ b/some_ip_sd_entries/lua.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -368,7 +368,7 @@ <h3>some_ip_sd_entries.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/nim.html b/some_ip_sd_entries/nim.html
index 32227f9e7..841b51b0a 100644
--- a/some_ip_sd_entries/nim.html
+++ b/some_ip_sd_entries/nim.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -417,7 +417,7 @@ <h3>some_ip_sd_entries.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/perl.html b/some_ip_sd_entries/perl.html
index 4a965b04d..a884b1644 100644
--- a/some_ip_sd_entries/perl.html
+++ b/some_ip_sd_entries/perl.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -548,7 +548,7 @@ <h3>SomeIpSdEntries.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/php.html b/some_ip_sd_entries/php.html
index b2fbac1ae..244648cfa 100644
--- a/some_ip_sd_entries/php.html
+++ b/some_ip_sd_entries/php.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -401,7 +401,7 @@ <h3>SomeIpSdEntries.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/python.html b/some_ip_sd_entries/python.html
index ed36d88ec..ca50e7d72 100644
--- a/some_ip_sd_entries/python.html
+++ b/some_ip_sd_entries/python.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -397,7 +397,7 @@ <h3>some_ip_sd_entries.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_entries/ruby.html b/some_ip_sd_entries/ruby.html
index bf8cb1465..1dde3ce44 100644
--- a/some_ip_sd_entries/ruby.html
+++ b/some_ip_sd_entries/ruby.html
@@ -105,7 +105,7 @@ <h1>AUTOSAR SOME/IP Service Discovery Entries:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The entries are used to synchronize the state of services instances and the
+                <p><p>The entries are used to synchronize the state of services instances and the<br />
 Publish/-Subscribe handling.</p>
 </p>
             </div>
@@ -417,7 +417,7 @@ <h3>some_ip_sd_entries.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/cpp_stl_11.html b/some_ip_sd_options/cpp_stl_11.html
index a99da178c..0092a3b57 100644
--- a/some_ip_sd_options/cpp_stl_11.html
+++ b/some_ip_sd_options/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -1162,7 +1162,7 @@ <h3>some_ip_sd_options.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/cpp_stl_98.html b/some_ip_sd_options/cpp_stl_98.html
index bb0460a79..e4edb4b1b 100644
--- a/some_ip_sd_options/cpp_stl_98.html
+++ b/some_ip_sd_options/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -1278,7 +1278,7 @@ <h3>some_ip_sd_options.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/csharp.html b/some_ip_sd_options/csharp.html
index 668b99f63..1aec3a548 100644
--- a/some_ip_sd_options/csharp.html
+++ b/some_ip_sd_options/csharp.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -809,7 +809,7 @@ <h3>SomeIpSdOptions.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/go.html b/some_ip_sd_options/go.html
index 861dcaed5..de8283260 100644
--- a/some_ip_sd_options/go.html
+++ b/some_ip_sd_options/go.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -888,7 +888,7 @@ <h3>some_ip_sd_options.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/graphviz.html b/some_ip_sd_options/graphviz.html
index b1508e2b9..8fd84643c 100644
--- a/some_ip_sd_options/graphviz.html
+++ b/some_ip_sd_options/graphviz.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -443,7 +443,7 @@ <h3>some_ip_sd_options.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/index.html b/some_ip_sd_options/index.html
index 404606a2c..1941baa9d 100644
--- a/some_ip_sd_options/index.html
+++ b/some_ip_sd_options/index.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -418,7 +418,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/java.html b/some_ip_sd_options/java.html
index 657151421..0a9024a75 100644
--- a/some_ip_sd_options/java.html
+++ b/some_ip_sd_options/java.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -897,7 +897,7 @@ <h3>SomeIpSdOptions.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/javascript.html b/some_ip_sd_options/javascript.html
index 47301d390..e3eeb135b 100644
--- a/some_ip_sd_options/javascript.html
+++ b/some_ip_sd_options/javascript.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -613,7 +613,7 @@ <h3>SomeIpSdOptions.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/lua.html b/some_ip_sd_options/lua.html
index cb79ac275..ebf5c5ec3 100644
--- a/some_ip_sd_options/lua.html
+++ b/some_ip_sd_options/lua.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -537,7 +537,7 @@ <h3>some_ip_sd_options.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/nim.html b/some_ip_sd_options/nim.html
index 817c93dbf..ad9b301e3 100644
--- a/some_ip_sd_options/nim.html
+++ b/some_ip_sd_options/nim.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -662,7 +662,7 @@ <h3>some_ip_sd_options.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/perl.html b/some_ip_sd_options/perl.html
index c1b1e03de..038c725a5 100644
--- a/some_ip_sd_options/perl.html
+++ b/some_ip_sd_options/perl.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -1033,7 +1033,7 @@ <h3>SomeIpSdOptions.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/php.html b/some_ip_sd_options/php.html
index 8f8c8a761..d6fbbf4fe 100644
--- a/some_ip_sd_options/php.html
+++ b/some_ip_sd_options/php.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -621,7 +621,7 @@ <h3>SomeIpSdOptions.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/python.html b/some_ip_sd_options/python.html
index da877855c..0cb285b32 100644
--- a/some_ip_sd_options/python.html
+++ b/some_ip_sd_options/python.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -537,7 +537,7 @@ <h3>some_ip_sd_options.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/some_ip_sd_options/ruby.html b/some_ip_sd_options/ruby.html
index ea0ca59f4..0e278ff71 100644
--- a/some_ip_sd_options/ruby.html
+++ b/some_ip_sd_options/ruby.html
@@ -105,8 +105,8 @@ <h1>AUTOSAR SOME/IP Service Discovery Options:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>FormatOptions are used to transport additional information to the entries.
-This includes forinstance the information how a service instance is
+                <p><p>FormatOptions are used to transport additional information to the entries.<br />
+This includes forinstance the information how a service instance is<br />
 reachable (IP-Address, TransportProtocol, Port Number).</p>
 </p>
             </div>
@@ -586,7 +586,7 @@ <h3>some_ip_sd_options.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/cpp_stl_11.html b/specpr/cpp_stl_11.html
index 5264772b0..52984d89d 100644
--- a/specpr/cpp_stl_11.html
+++ b/specpr/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1302,7 +1302,7 @@ <h3>specpr.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/cpp_stl_98.html b/specpr/cpp_stl_98.html
index e6703de1d..edb88cab4 100644
--- a/specpr/cpp_stl_98.html
+++ b/specpr/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1412,7 +1412,7 @@ <h3>specpr.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/csharp.html b/specpr/csharp.html
index 7908345b8..f1e429835 100644
--- a/specpr/csharp.html
+++ b/specpr/csharp.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1022,7 +1022,7 @@ <h3>Specpr.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/go.html b/specpr/go.html
index acbcbd5e6..b2c4b2343 100644
--- a/specpr/go.html
+++ b/specpr/go.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1126,7 +1126,7 @@ <h3>specpr.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/graphviz.html b/specpr/graphviz.html
index 679ab4125..983f3b39d 100644
--- a/specpr/graphviz.html
+++ b/specpr/graphviz.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -451,7 +451,7 @@ <h3>specpr.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/index.html b/specpr/index.html
index 2b809ea2c..5be6e866d 100644
--- a/specpr/index.html
+++ b/specpr/index.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -510,7 +510,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/java.html b/specpr/java.html
index 49f971d37..7e8d7a410 100644
--- a/specpr/java.html
+++ b/specpr/java.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1053,7 +1053,7 @@ <h3>Specpr.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/javascript.html b/specpr/javascript.html
index 41e2077e4..894abd0fe 100644
--- a/specpr/javascript.html
+++ b/specpr/javascript.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -811,7 +811,7 @@ <h3>Specpr.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/lua.html b/specpr/lua.html
index ae8c8f9ad..a4f7056a5 100644
--- a/specpr/lua.html
+++ b/specpr/lua.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -669,7 +669,7 @@ <h3>specpr.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/nim.html b/specpr/nim.html
index 7a5ac5425..7d7c96a63 100644
--- a/specpr/nim.html
+++ b/specpr/nim.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -891,7 +891,7 @@ <h3>specpr.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/perl.html b/specpr/perl.html
index 473a8039e..168ed58f3 100644
--- a/specpr/perl.html
+++ b/specpr/perl.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -976,7 +976,7 @@ <h3>Specpr.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/php.html b/specpr/php.html
index 375417b8b..3b47e6b75 100644
--- a/specpr/php.html
+++ b/specpr/php.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -837,7 +837,7 @@ <h3>Specpr.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/python.html b/specpr/python.html
index fb77931aa..8a655bc50 100644
--- a/specpr/python.html
+++ b/specpr/python.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -561,7 +561,7 @@ <h3>specpr.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/specpr/ruby.html b/specpr/ruby.html
index 97fa0f2ba..10be30224 100644
--- a/specpr/ruby.html
+++ b/specpr/ruby.html
@@ -105,14 +105,14 @@ <h1>SPECtrum Processing Routines Data Format 3/4/88:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number
-counting starts at 0. Binary data are in IEEE format real numbers
-and non-byte swapped integers (compatiible with all Sun
-Microsystems, and Hewlett Packard workstations (Intel and some DEC
-machines are byte swapped relative to Suns and HPs). Each record may
+                <p><p>Specpr records are fixed format, 1536 bytes/record. Record number<br />
+counting starts at 0. Binary data are in IEEE format real numbers<br />
+and non-byte swapped integers (compatiible with all Sun<br />
+Microsystems, and Hewlett Packard workstations (Intel and some DEC<br />
+machines are byte swapped relative to Suns and HPs). Each record may<br />
 contain different information according to the following scheme.</p>
-<p>You can get some library of spectra from
-ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</p>
+<p>You can get some library of spectra from<br />
+<a href="ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/">ftp://ftpext.cr.usgs.gov/pub/cr/co/denver/speclab/pub/spectral.library/splib06.library/</a></p>
 </p>
             </div>
             <div class="col-md-4">
@@ -747,7 +747,7 @@ <h3>specpr.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/cpp_stl_11.html b/sqlite3/cpp_stl_11.html
index 34bedc5e0..3c4821076 100644
--- a/sqlite3/cpp_stl_11.html
+++ b/sqlite3/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -1366,7 +1366,7 @@ <h3>sqlite3.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/cpp_stl_98.html b/sqlite3/cpp_stl_98.html
index 4860215b0..9a87e43c4 100644
--- a/sqlite3/cpp_stl_98.html
+++ b/sqlite3/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -1503,7 +1503,7 @@ <h3>sqlite3.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/csharp.html b/sqlite3/csharp.html
index 5ddacb64a..92aa4b278 100644
--- a/sqlite3/csharp.html
+++ b/sqlite3/csharp.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -998,7 +998,7 @@ <h3>Sqlite3.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/index.html b/sqlite3/index.html
index e123b87c5..5c6c90067 100644
--- a/sqlite3/index.html
+++ b/sqlite3/index.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -508,7 +508,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/java.html b/sqlite3/java.html
index e10d1f033..72cd3e709 100644
--- a/sqlite3/java.html
+++ b/sqlite3/java.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -1037,7 +1037,7 @@ <h3>Sqlite3.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/javascript.html b/sqlite3/javascript.html
index abb9de8f5..2aae0c972 100644
--- a/sqlite3/javascript.html
+++ b/sqlite3/javascript.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -768,7 +768,7 @@ <h3>Sqlite3.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/lua.html b/sqlite3/lua.html
index 9b9b4d641..cc0cc3bf0 100644
--- a/sqlite3/lua.html
+++ b/sqlite3/lua.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -667,7 +667,7 @@ <h3>sqlite3.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/nim.html b/sqlite3/nim.html
index a68d83502..84f13ba5d 100644
--- a/sqlite3/nim.html
+++ b/sqlite3/nim.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -840,7 +840,7 @@ <h3>sqlite3.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/perl.html b/sqlite3/perl.html
index 0eecfb8bd..678d8b660 100644
--- a/sqlite3/perl.html
+++ b/sqlite3/perl.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -1080,7 +1080,7 @@ <h3>Sqlite3.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/php.html b/sqlite3/php.html
index 3d7c4e3db..986d010a0 100644
--- a/sqlite3/php.html
+++ b/sqlite3/php.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -779,7 +779,7 @@ <h3>Sqlite3.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/python.html b/sqlite3/python.html
index b23d505bf..d55846c2a 100644
--- a/sqlite3/python.html
+++ b/sqlite3/python.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -642,7 +642,7 @@ <h3>sqlite3.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sqlite3/ruby.html b/sqlite3/ruby.html
index f70d48bd8..59b36b550 100644
--- a/sqlite3/ruby.html
+++ b/sqlite3/ruby.html
@@ -105,16 +105,16 @@ <h1>SQLite3 database file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library
-to be used within other applications. It keeps its databases as
+                <p><p>SQLite3 is a popular serverless SQL engine, implemented as a library<br />
+to be used within other applications. It keeps its databases as<br />
 regular disk files.</p>
-<p>Every database file is segmented into pages. First page (starting at
-the very beginning) is special: it contains a file-global header
-which specifies some data relevant to proper parsing (i.e. format
-versions, size of page, etc). After the header, normal contents of
+<p>Every database file is segmented into pages. First page (starting at<br />
+the very beginning) is special: it contains a file-global header<br />
+which specifies some data relevant to proper parsing (i.e. format<br />
+versions, size of page, etc). After the header, normal contents of<br />
 the first page follow.</p>
-<p>Each page would be of some type, and generally, they would be
-reached via the links starting from the first page. First page type
+<p>Each page would be of some type, and generally, they would be<br />
+reached via the links starting from the first page. First page type<br />
 (<code>root_page</code>) is always &quot;btree_page&quot;.</p>
 </p>
             </div>
@@ -723,7 +723,7 @@ <h3>sqlite3.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/cpp_stl_11.html b/ssh_public_key/cpp_stl_11.html
index 08f8ddaeb..a7cf49dc0 100644
--- a/ssh_public_key/cpp_stl_11.html
+++ b/ssh_public_key/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -873,7 +873,7 @@ <h3>ssh_public_key.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/cpp_stl_98.html b/ssh_public_key/cpp_stl_98.html
index 53c032c4b..f53144cd6 100644
--- a/ssh_public_key/cpp_stl_98.html
+++ b/ssh_public_key/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -953,7 +953,7 @@ <h3>ssh_public_key.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/csharp.html b/ssh_public_key/csharp.html
index 00a043d41..a86296f71 100644
--- a/ssh_public_key/csharp.html
+++ b/ssh_public_key/csharp.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -655,7 +655,7 @@ <h3>SshPublicKey.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/go.html b/ssh_public_key/go.html
index 485501763..ec5ca0a39 100644
--- a/ssh_public_key/go.html
+++ b/ssh_public_key/go.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -641,7 +641,7 @@ <h3>ssh_public_key.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/graphviz.html b/ssh_public_key/graphviz.html
index a89e0a511..d7c6a64bd 100644
--- a/ssh_public_key/graphviz.html
+++ b/ssh_public_key/graphviz.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -375,7 +375,7 @@ <h3>ssh_public_key.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/index.html b/ssh_public_key/index.html
index 7dc914519..f2023e158 100644
--- a/ssh_public_key/index.html
+++ b/ssh_public_key/index.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -362,7 +362,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/java.html b/ssh_public_key/java.html
index f0b73c435..0af4d621c 100644
--- a/ssh_public_key/java.html
+++ b/ssh_public_key/java.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -678,7 +678,7 @@ <h3>SshPublicKey.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/javascript.html b/ssh_public_key/javascript.html
index 6d4544c4e..4a15fc7e1 100644
--- a/ssh_public_key/javascript.html
+++ b/ssh_public_key/javascript.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -541,7 +541,7 @@ <h3>SshPublicKey.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/lua.html b/ssh_public_key/lua.html
index faf44e0bf..e31d47cca 100644
--- a/ssh_public_key/lua.html
+++ b/ssh_public_key/lua.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -464,7 +464,7 @@ <h3>ssh_public_key.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/nim.html b/ssh_public_key/nim.html
index 3aa7fc82f..6eadd2909 100644
--- a/ssh_public_key/nim.html
+++ b/ssh_public_key/nim.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -551,7 +551,7 @@ <h3>ssh_public_key.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/perl.html b/ssh_public_key/perl.html
index 90e562bda..7e75dc2e1 100644
--- a/ssh_public_key/perl.html
+++ b/ssh_public_key/perl.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -651,7 +651,7 @@ <h3>SshPublicKey.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/php.html b/ssh_public_key/php.html
index 28f59a4af..b6ce07549 100644
--- a/ssh_public_key/php.html
+++ b/ssh_public_key/php.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -486,7 +486,7 @@ <h3>SshPublicKey.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/python.html b/ssh_public_key/python.html
index d148674f0..8140b81c9 100644
--- a/ssh_public_key/python.html
+++ b/ssh_public_key/python.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -487,7 +487,7 @@ <h3>ssh_public_key.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ssh_public_key/ruby.html b/ssh_public_key/ruby.html
index d7623efc9..fd8a85bb7 100644
--- a/ssh_public_key/ruby.html
+++ b/ssh_public_key/ruby.html
@@ -105,13 +105,13 @@ <h1>SSH public key:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SSH public keys are encoded in a special binary format, typically represented
-to end users as either one-liner OpenSSH format or multi-line PEM format
-(commerical SSH). Text wrapper carries extra information about user who
-created the key, comment, etc, but the inner binary is always base64-encoded
+                <p><p>SSH public keys are encoded in a special binary format, typically represented<br />
+to end users as either one-liner OpenSSH format or multi-line PEM format<br />
+(commerical SSH). Text wrapper carries extra information about user who<br />
+created the key, comment, etc, but the inner binary is always base64-encoded<br />
 and follows the same internal format.</p>
-<p>This format spec deals with this internal binary format (called &quot;blob&quot; in
-openssh sources) only. Buffer is expected to be raw binary and not base64-d.
+<p>This format spec deals with this internal binary format (called &quot;blob&quot; in<br />
+openssh sources) only. Buffer is expected to be raw binary and not base64-d.<br />
 Implementation closely follows code in OpenSSH.</p>
 </p>
             </div>
@@ -504,7 +504,7 @@ <h3>ssh_public_key.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/cpp_stl_11.html b/standard_midi_file/cpp_stl_11.html
index 599699535..150067606 100644
--- a/standard_midi_file/cpp_stl_11.html
+++ b/standard_midi_file/cpp_stl_11.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -1257,7 +1257,7 @@ <h3>standard_midi_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/cpp_stl_98.html b/standard_midi_file/cpp_stl_98.html
index 4608f13c4..051ea8a33 100644
--- a/standard_midi_file/cpp_stl_98.html
+++ b/standard_midi_file/cpp_stl_98.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -1382,7 +1382,7 @@ <h3>standard_midi_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/csharp.html b/standard_midi_file/csharp.html
index 5904859e4..434b48433 100644
--- a/standard_midi_file/csharp.html
+++ b/standard_midi_file/csharp.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -881,7 +881,7 @@ <h3>StandardMidiFile.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/go.html b/standard_midi_file/go.html
index 3d7225c4b..c9ed35e82 100644
--- a/standard_midi_file/go.html
+++ b/standard_midi_file/go.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -919,7 +919,7 @@ <h3>standard_midi_file.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/graphviz.html b/standard_midi_file/graphviz.html
index 468f2f705..9d94a8adb 100644
--- a/standard_midi_file/graphviz.html
+++ b/standard_midi_file/graphviz.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -493,7 +493,7 @@ <h3>standard_midi_file.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/index.html b/standard_midi_file/index.html
index b3490f29c..8af56f191 100644
--- a/standard_midi_file/index.html
+++ b/standard_midi_file/index.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/java.html b/standard_midi_file/java.html
index b42068c7c..9b92aeba4 100644
--- a/standard_midi_file/java.html
+++ b/standard_midi_file/java.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -939,7 +939,7 @@ <h3>StandardMidiFile.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/javascript.html b/standard_midi_file/javascript.html
index 7c15788a3..205f7a836 100644
--- a/standard_midi_file/javascript.html
+++ b/standard_midi_file/javascript.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -696,7 +696,7 @@ <h3>StandardMidiFile.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/lua.html b/standard_midi_file/lua.html
index 3d433302e..49a2b484b 100644
--- a/standard_midi_file/lua.html
+++ b/standard_midi_file/lua.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -622,7 +622,7 @@ <h3>standard_midi_file.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/nim.html b/standard_midi_file/nim.html
index f10928788..79b7671a1 100644
--- a/standard_midi_file/nim.html
+++ b/standard_midi_file/nim.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>standard_midi_file.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/perl.html b/standard_midi_file/perl.html
index cc4532d57..6ea3d2b61 100644
--- a/standard_midi_file/perl.html
+++ b/standard_midi_file/perl.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -1028,7 +1028,7 @@ <h3>StandardMidiFile.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/php.html b/standard_midi_file/php.html
index 65c8b16dc..c2ad68553 100644
--- a/standard_midi_file/php.html
+++ b/standard_midi_file/php.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -670,7 +670,7 @@ <h3>StandardMidiFile.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/python.html b/standard_midi_file/python.html
index 2c88df2d9..3cf95fe21 100644
--- a/standard_midi_file/python.html
+++ b/standard_midi_file/python.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -612,7 +612,7 @@ <h3>standard_midi_file.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/standard_midi_file/ruby.html b/standard_midi_file/ruby.html
index 46f564ec3..b9f5aec1f 100644
--- a/standard_midi_file/ruby.html
+++ b/standard_midi_file/ruby.html
@@ -105,17 +105,17 @@ <h1>Standard MIDI file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way
-to serialize series of MIDI events, which is a protocol used in many
-music synthesizers to transfer music data: notes being played,
+                <p><p>Standard MIDI file, typically known just as &quot;MID&quot;, is a standard way<br />
+to serialize series of MIDI events, which is a protocol used in many<br />
+music synthesizers to transfer music data: notes being played,<br />
 effects being applied, etc.</p>
-<p>Internally, file consists of a header and series of tracks, every
-track listing MIDI events with certain header designating time these
+<p>Internally, file consists of a header and series of tracks, every<br />
+track listing MIDI events with certain header designating time these<br />
 events are happening.</p>
-<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme
-to avoid storing certain elements of further elements, instead
-reusing them from events which happened earlier in the
-stream. Kaitai Struct (as of v0.9) is currently unable to parse
+<p>NOTE: Rarely, MIDI files employ certain stateful compression scheme<br />
+to avoid storing certain elements of further elements, instead<br />
+reusing them from events which happened earlier in the<br />
+stream. Kaitai Struct (as of v0.9) is currently unable to parse<br />
 these, but files employing this mechanism are relatively rare.</p>
 </p>
             </div>
@@ -634,7 +634,7 @@ <h3>standard_midi_file.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/cpp_stl_11.html b/stl/cpp_stl_11.html
index 74b060952..3e31db06a 100644
--- a/stl/cpp_stl_11.html
+++ b/stl/cpp_stl_11.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -596,7 +596,7 @@ <h3>stl.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/cpp_stl_98.html b/stl/cpp_stl_98.html
index 301c4e1ff..1e11d8304 100644
--- a/stl/cpp_stl_98.html
+++ b/stl/cpp_stl_98.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -631,7 +631,7 @@ <h3>stl.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/csharp.html b/stl/csharp.html
index 8d0799926..391e94f08 100644
--- a/stl/csharp.html
+++ b/stl/csharp.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -479,7 +479,7 @@ <h3>Stl.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/go.html b/stl/go.html
index f0206d7f8..e793ae844 100644
--- a/stl/go.html
+++ b/stl/go.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -451,7 +451,7 @@ <h3>stl.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/graphviz.html b/stl/graphviz.html
index a2bc8b3cb..61a4ffe81 100644
--- a/stl/graphviz.html
+++ b/stl/graphviz.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -339,7 +339,7 @@ <h3>stl.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/index.html b/stl/index.html
index 330b2c536..6fc375129 100644
--- a/stl/index.html
+++ b/stl/index.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -352,7 +352,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/java.html b/stl/java.html
index 42f9f5402..13e0f8239 100644
--- a/stl/java.html
+++ b/stl/java.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -495,7 +495,7 @@ <h3>Stl.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/javascript.html b/stl/javascript.html
index 91090c73e..f19b3bd41 100644
--- a/stl/javascript.html
+++ b/stl/javascript.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -440,7 +440,7 @@ <h3>Stl.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/lua.html b/stl/lua.html
index fb7e6dfec..6df45777e 100644
--- a/stl/lua.html
+++ b/stl/lua.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -385,7 +385,7 @@ <h3>stl.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/nim.html b/stl/nim.html
index 1099cb1c7..23cf35aff 100644
--- a/stl/nim.html
+++ b/stl/nim.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -415,7 +415,7 @@ <h3>stl.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/perl.html b/stl/perl.html
index 44430a1c9..c064dc90d 100644
--- a/stl/perl.html
+++ b/stl/perl.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h3>Stl.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/php.html b/stl/php.html
index a18ebd4d7..c28d069ce 100644
--- a/stl/php.html
+++ b/stl/php.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -405,7 +405,7 @@ <h3>Stl.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/python.html b/stl/python.html
index d6b1acd9f..23a6e9e5f 100644
--- a/stl/python.html
+++ b/stl/python.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -412,7 +412,7 @@ <h3>stl.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/stl/ruby.html b/stl/ruby.html
index a728153a7..4ecf005bf 100644
--- a/stl/ruby.html
+++ b/stl/ruby.html
@@ -105,18 +105,18 @@ <h1>.stl file format of 3D Systems Stereolithography:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>STL files are used to represent simple 3D models, defined using
+                <p><p>STL files are used to represent simple 3D models, defined using<br />
 triangular 3D faces.</p>
-<p>Initially it was introduced as native format for 3D Systems
-Stereolithography CAD system, but due to its extreme simplicity, it
-was adopted by a wide range of 3D modelling, CAD, rapid prototyping
-and 3D printing applications as the simplest 3D model exchange
+<p>Initially it was introduced as native format for 3D Systems<br />
+Stereolithography CAD system, but due to its extreme simplicity, it<br />
+was adopted by a wide range of 3D modelling, CAD, rapid prototyping<br />
+and 3D printing applications as the simplest 3D model exchange<br />
 format.</p>
-<p>STL is extremely bare-bones format: there are no complex headers, no
-texture / color support, no units specifications, no distinct vertex
-arrays. Whole model is specified as a collection of triangular
+<p>STL is extremely bare-bones format: there are no complex headers, no<br />
+texture / color support, no units specifications, no distinct vertex<br />
+arrays. Whole model is specified as a collection of triangular<br />
 faces.</p>
-<p>There are two versions of the format (text and binary), this spec
+<p>There are two versions of the format (text and binary), this spec<br />
 describes binary version.</p>
 </p>
             </div>
@@ -433,7 +433,7 @@ <h3>stl.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/cpp_stl_11.html b/sudoers_ts/cpp_stl_11.html
index 6ff9cb629..d1ccdff01 100644
--- a/sudoers_ts/cpp_stl_11.html
+++ b/sudoers_ts/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -864,7 +864,7 @@ <h3>sudoers_ts.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/cpp_stl_98.html b/sudoers_ts/cpp_stl_98.html
index e4fa5a364..72094770b 100644
--- a/sudoers_ts/cpp_stl_98.html
+++ b/sudoers_ts/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -929,7 +929,7 @@ <h3>sudoers_ts.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/csharp.html b/sudoers_ts/csharp.html
index a50cae845..2fb7b335f 100644
--- a/sudoers_ts/csharp.html
+++ b/sudoers_ts/csharp.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -639,7 +639,7 @@ <h3>SudoersTs.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/go.html b/sudoers_ts/go.html
index 1b76e045a..6702e41c7 100644
--- a/sudoers_ts/go.html
+++ b/sudoers_ts/go.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -668,7 +668,7 @@ <h3>sudoers_ts.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/graphviz.html b/sudoers_ts/graphviz.html
index 85d6715f5..73ac62de6 100644
--- a/sudoers_ts/graphviz.html
+++ b/sudoers_ts/graphviz.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -340,7 +340,7 @@ <h3>sudoers_ts.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/index.html b/sudoers_ts/index.html
index c56a53ad4..9230b12b3 100644
--- a/sudoers_ts/index.html
+++ b/sudoers_ts/index.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -351,7 +351,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/java.html b/sudoers_ts/java.html
index 2f7323585..48b467365 100644
--- a/sudoers_ts/java.html
+++ b/sudoers_ts/java.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -681,7 +681,7 @@ <h3>SudoersTs.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/javascript.html b/sudoers_ts/javascript.html
index efdc7526b..0d2a55a9a 100644
--- a/sudoers_ts/javascript.html
+++ b/sudoers_ts/javascript.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -544,7 +544,7 @@ <h3>SudoersTs.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/lua.html b/sudoers_ts/lua.html
index f9703aedb..890e9068f 100644
--- a/sudoers_ts/lua.html
+++ b/sudoers_ts/lua.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -439,7 +439,7 @@ <h3>sudoers_ts.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/nim.html b/sudoers_ts/nim.html
index 27df0eec7..dce8bce3c 100644
--- a/sudoers_ts/nim.html
+++ b/sudoers_ts/nim.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -546,7 +546,7 @@ <h3>sudoers_ts.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/perl.html b/sudoers_ts/perl.html
index 76e7a3bed..7fed8ae66 100644
--- a/sudoers_ts/perl.html
+++ b/sudoers_ts/perl.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -630,7 +630,7 @@ <h3>SudoersTs.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/php.html b/sudoers_ts/php.html
index 3e0ec9a1a..7b150ccc4 100644
--- a/sudoers_ts/php.html
+++ b/sudoers_ts/php.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -531,7 +531,7 @@ <h3>SudoersTs.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/python.html b/sudoers_ts/python.html
index 4498ee2e9..84da13ab4 100644
--- a/sudoers_ts/python.html
+++ b/sudoers_ts/python.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -418,7 +418,7 @@ <h3>sudoers_ts.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/sudoers_ts/ruby.html b/sudoers_ts/ruby.html
index 17df7c99b..d13d30e89 100644
--- a/sudoers_ts/ruby.html
+++ b/sudoers_ts/ruby.html
@@ -105,7 +105,7 @@ <h1>Sudoers Time Stamp file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This spec can be used to parse sudo time stamp files located in directories
+                <p><p>This spec can be used to parse sudo time stamp files located in directories<br />
 such as /run/sudo/ts/$USER or /var/lib/sudo/ts/$USER.</p>
 </p>
             </div>
@@ -514,7 +514,7 @@ <h3>sudoers_ts.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/cpp_stl_11.html b/swf/cpp_stl_11.html
index 787785779..9a54c8a96 100644
--- a/swf/cpp_stl_11.html
+++ b/swf/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -1241,7 +1241,7 @@ <h3>swf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/cpp_stl_98.html b/swf/cpp_stl_98.html
index aace47677..9dc8ce310 100644
--- a/swf/cpp_stl_98.html
+++ b/swf/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -1348,7 +1348,7 @@ <h3>swf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/csharp.html b/swf/csharp.html
index 769348aaa..04ba12620 100644
--- a/swf/csharp.html
+++ b/swf/csharp.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -891,7 +891,7 @@ <h3>Swf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/go.html b/swf/go.html
index 812204907..667290db4 100644
--- a/swf/go.html
+++ b/swf/go.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -1013,7 +1013,7 @@ <h3>swf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/graphviz.html b/swf/graphviz.html
index 0ee5ae46a..146291b78 100644
--- a/swf/graphviz.html
+++ b/swf/graphviz.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -470,7 +470,7 @@ <h3>swf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/index.html b/swf/index.html
index cf69fa9dd..77108392f 100644
--- a/swf/index.html
+++ b/swf/index.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -487,7 +487,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/java.html b/swf/java.html
index 8ae85365d..393d48ebf 100644
--- a/swf/java.html
+++ b/swf/java.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -970,7 +970,7 @@ <h3>Swf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/javascript.html b/swf/javascript.html
index 27d421751..95cfb8aa5 100644
--- a/swf/javascript.html
+++ b/swf/javascript.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -723,7 +723,7 @@ <h3>Swf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/lua.html b/swf/lua.html
index 751923409..8021ecd09 100644
--- a/swf/lua.html
+++ b/swf/lua.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -636,7 +636,7 @@ <h3>swf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/nim.html b/swf/nim.html
index 8ecd3f350..5dc81d0c6 100644
--- a/swf/nim.html
+++ b/swf/nim.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -734,7 +734,7 @@ <h3>swf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/perl.html b/swf/perl.html
index ec0b9c03a..18a4eb2d7 100644
--- a/swf/perl.html
+++ b/swf/perl.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -1001,7 +1001,7 @@ <h3>Swf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/php.html b/swf/php.html
index 4d06d563f..937b3fbba 100644
--- a/swf/php.html
+++ b/swf/php.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -702,7 +702,7 @@ <h3>Swf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/python.html b/swf/python.html
index 59e57b3a7..1b0e84508 100644
--- a/swf/python.html
+++ b/swf/python.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -629,7 +629,7 @@ <h3>swf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/swf/ruby.html b/swf/ruby.html
index d653065a5..36654e6a3 100644
--- a/swf/ruby.html
+++ b/swf/ruby.html
@@ -105,16 +105,16 @@ <h1>Adobe Flash (AKA Shockwave Flash, Macromedia Flash):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia
-Flash) to encode rich interactive multimedia content and are,
-essentially, a container for special bytecode instructions to play
-back that content. In early 2000s, it was dominant rich multimedia
-web format (.swf files were integrated into web pages and played
-back with a browser plugin), but its usage largely declined in
-2010s, as HTML5 and performant browser-native solutions
-(i.e. JavaScript engines and graphical approaches, such as WebGL)
+                <p><p>SWF files are used by Adobe Flash (AKA Shockwave Flash, Macromedia<br />
+Flash) to encode rich interactive multimedia content and are,<br />
+essentially, a container for special bytecode instructions to play<br />
+back that content. In early 2000s, it was dominant rich multimedia<br />
+web format (.swf files were integrated into web pages and played<br />
+back with a browser plugin), but its usage largely declined in<br />
+2010s, as HTML5 and performant browser-native solutions<br />
+(i.e. JavaScript engines and graphical approaches, such as WebGL)<br />
 emerged.</p>
-<p>There are a lot of versions of SWF (~36), format is somewhat
+<p>There are a lot of versions of SWF (~36), format is somewhat<br />
 documented by Adobe.</p>
 </p>
             </div>
@@ -664,7 +664,7 @@ <h3>swf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/cpp_stl_11.html b/systemd_journal/cpp_stl_11.html
index 2dc0fd1da..5c9df7ee5 100644
--- a/systemd_journal/cpp_stl_11.html
+++ b/systemd_journal/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -1009,7 +1009,7 @@ <h3>systemd_journal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/cpp_stl_98.html b/systemd_journal/cpp_stl_98.html
index 35740cb9a..401b93e86 100644
--- a/systemd_journal/cpp_stl_98.html
+++ b/systemd_journal/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -1065,7 +1065,7 @@ <h3>systemd_journal.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/csharp.html b/systemd_journal/csharp.html
index dda59a7b4..bd9d76c4b 100644
--- a/systemd_journal/csharp.html
+++ b/systemd_journal/csharp.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -761,7 +761,7 @@ <h3>SystemdJournal.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/go.html b/systemd_journal/go.html
index fb39f0a76..54d38e2a2 100644
--- a/systemd_journal/go.html
+++ b/systemd_journal/go.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -951,7 +951,7 @@ <h3>systemd_journal.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/graphviz.html b/systemd_journal/graphviz.html
index 058d6dfa9..e47688ea6 100644
--- a/systemd_journal/graphviz.html
+++ b/systemd_journal/graphviz.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -415,7 +415,7 @@ <h3>systemd_journal.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/index.html b/systemd_journal/index.html
index b4ee814db..8cb80db88 100644
--- a/systemd_journal/index.html
+++ b/systemd_journal/index.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -482,7 +482,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/java.html b/systemd_journal/java.html
index edeab6ab9..d1d039a4a 100644
--- a/systemd_journal/java.html
+++ b/systemd_journal/java.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -757,7 +757,7 @@ <h3>SystemdJournal.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/javascript.html b/systemd_journal/javascript.html
index b4b7eebe1..369b57dc4 100644
--- a/systemd_journal/javascript.html
+++ b/systemd_journal/javascript.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -606,7 +606,7 @@ <h3>SystemdJournal.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/lua.html b/systemd_journal/lua.html
index fada78acc..67de18639 100644
--- a/systemd_journal/lua.html
+++ b/systemd_journal/lua.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -548,7 +548,7 @@ <h3>systemd_journal.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/nim.html b/systemd_journal/nim.html
index 10d48cee2..5c4c9dfa6 100644
--- a/systemd_journal/nim.html
+++ b/systemd_journal/nim.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -647,7 +647,7 @@ <h3>systemd_journal.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/perl.html b/systemd_journal/perl.html
index df38af8e9..0df17a821 100644
--- a/systemd_journal/perl.html
+++ b/systemd_journal/perl.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -804,7 +804,7 @@ <h3>SystemdJournal.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/php.html b/systemd_journal/php.html
index 87e4d871a..1f603ce5b 100644
--- a/systemd_journal/php.html
+++ b/systemd_journal/php.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -629,7 +629,7 @@ <h3>SystemdJournal.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/python.html b/systemd_journal/python.html
index 250f2e166..3614c8ac1 100644
--- a/systemd_journal/python.html
+++ b/systemd_journal/python.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -570,7 +570,7 @@ <h3>systemd_journal.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/systemd_journal/ruby.html b/systemd_journal/ruby.html
index f7a1ed8ea..4f9b522ec 100644
--- a/systemd_journal/ruby.html
+++ b/systemd_journal/ruby.html
@@ -105,8 +105,8 @@ <h1>systemd journal file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>systemd, a popular user-space system/service management suite on Linux,
-offers logging functionality, storing incoming logs in a binary journal
+                <p><p>systemd, a popular user-space system/service management suite on Linux,<br />
+offers logging functionality, storing incoming logs in a binary journal<br />
 format.</p>
 <p>On live Linux system running systemd, these journals are typically located at:</p>
 <ul>
@@ -594,7 +594,7 @@ <h3>systemd_journal.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/cpp_stl_11.html b/tcp_segment/cpp_stl_11.html
index 84e3a3bf3..4e9339733 100644
--- a/tcp_segment/cpp_stl_11.html
+++ b/tcp_segment/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -316,7 +321,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by invoking getter methods like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -366,6 +371,7 @@ <h3>tcp_segment.h</h3>
 <span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">public</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="w"> </span><span class="p">{</span>
 
 <span class="k">public</span><span class="o">:</span>
+<span class="w">    </span><span class="k">class</span><span class="w"> </span><span class="nc">flags_t</span><span class="p">;</span>
 
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">nullptr</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">nullptr</span><span class="p">);</span>
 
@@ -376,30 +382,134 @@ <h3>tcp_segment.h</h3>
 <span class="k">public</span><span class="o">:</span>
 <span class="w">    </span><span class="o">~</span><span class="n">tcp_segment_t</span><span class="p">();</span>
 
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="k">class</span><span class="w"> </span><span class="nc">flags_t</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">public</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="w"> </span><span class="p">{</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+
+<span class="w">        </span><span class="n">flags_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">nullptr</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">nullptr</span><span class="p">);</span>
+
+<span class="w">    </span><span class="k">private</span><span class="o">:</span>
+<span class="w">        </span><span class="kt">void</span><span class="w"> </span><span class="n">_read</span><span class="p">();</span>
+<span class="w">        </span><span class="kt">void</span><span class="w"> </span><span class="nf">_clean_up</span><span class="p">();</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+<span class="w">        </span><span class="o">~</span><span class="n">flags_t</span><span class="p">();</span>
+
+<span class="w">    </span><span class="k">private</span><span class="o">:</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_cwr</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_ece</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_urg</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_ack</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_psh</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_rst</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_syn</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_fin</span><span class="p">;</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Congestion Window Reduced</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">cwr</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_cwr</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * ECN-Echo</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">ece</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ece</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Urgent pointer field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">urg</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_urg</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Acknowledgment field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">ack</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ack</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Push function</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">psh</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_psh</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Reset the connection</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">rst</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_rst</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Synchronize sequence numbers</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">syn</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_syn</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * No more data from sender</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">fin</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_fin</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_root</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_parent</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="p">};</span>
+
 <span class="k">private</span><span class="o">:</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_src_port</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_dst_port</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">m_seq_num</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">m_ack_num</span><span class="p">;</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">m_b12</span><span class="p">;</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">m_b13</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">m_data_offset</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">m_reserved</span><span class="p">;</span>
+<span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">unique_ptr</span><span class="o">&lt;</span><span class="n">flags_t</span><span class="o">&gt;</span><span class="w"> </span><span class="n">m_flags</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_window_size</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_checksum</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_urgent_pointer</span><span class="p">;</span>
+<span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">m_options</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">bool</span><span class="w"> </span><span class="n">n_options</span><span class="p">;</span>
+
+<span class="k">public</span><span class="o">:</span>
+<span class="w">    </span><span class="kt">bool</span><span class="w"> </span><span class="n">_is_null_options</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="n">options</span><span class="p">();</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">n_options</span><span class="p">;</span><span class="w"> </span><span class="p">};</span>
+
+<span class="k">private</span><span class="o">:</span>
 <span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">m_body</span><span class="p">;</span>
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span>
 <span class="w">    </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span>
 
 <span class="k">public</span><span class="o">:</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Source port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_src_port</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Destination port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">dst_port</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_dst_port</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Sequence number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">seq_num</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_seq_num</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Acknowledgment number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">ack_num</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ack_num</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">b12</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_b12</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">b13</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_b13</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="cm">     */</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_data_offset</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">reserved</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_reserved</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="n">flags_t</span><span class="o">*</span><span class="w"> </span><span class="n">flags</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_flags</span><span class="p">.</span><span class="n">get</span><span class="p">();</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">window_size</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_window_size</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">checksum</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_checksum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">urgent_pointer</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_urgent_pointer</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">options</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_options</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">body</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_body</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_root</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">_parent</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
@@ -427,6 +537,7 @@ <h3>tcp_segment.cpp</h3>
 <span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">tcp_segment_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="p">)</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="p">(</span><span class="n">p__io</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
 <span class="w">    </span><span class="n">m__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__parent</span><span class="p">;</span>
 <span class="w">    </span><span class="n">m__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">;</span>
+<span class="w">    </span><span class="n">m_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">nullptr</span><span class="p">;</span>
 <span class="w">    </span><span class="n">_read</span><span class="p">();</span>
 <span class="p">}</span>
 
@@ -435,11 +546,18 @@ <h3>tcp_segment.cpp</h3>
 <span class="w">    </span><span class="n">m_dst_port</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_seq_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_ack_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
-<span class="w">    </span><span class="n">m_b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
-<span class="w">    </span><span class="n">m_b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
+<span class="w">    </span><span class="n">m_data_offset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">align_to_byte</span><span class="p">();</span>
+<span class="w">    </span><span class="n">m_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">std</span><span class="o">::</span><span class="n">unique_ptr</span><span class="o">&lt;</span><span class="n">flags_t</span><span class="o">&gt;</span><span class="p">(</span><span class="k">new</span><span class="w"> </span><span class="n">flags_t</span><span class="p">(</span><span class="n">m__io</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="n">m__root</span><span class="p">));</span>
 <span class="w">    </span><span class="n">m_window_size</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_urgent_pointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
+<span class="w">    </span><span class="n">n_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nb">true</span><span class="p">;</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="n">n_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nb">false</span><span class="p">;</span>
+<span class="w">        </span><span class="n">m_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bytes</span><span class="p">(((</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">));</span>
+<span class="w">    </span><span class="p">}</span>
 <span class="w">    </span><span class="n">m_body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bytes_full</span><span class="p">();</span>
 <span class="p">}</span>
 
@@ -448,6 +566,32 @@ <h3>tcp_segment.cpp</h3>
 <span class="p">}</span>
 
 <span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">_clean_up</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(</span><span class="o">!</span><span class="n">n_options</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="p">}</span>
+<span class="p">}</span>
+
+<span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">flags_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="p">)</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="p">(</span><span class="n">p__io</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">m__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__parent</span><span class="p">;</span>
+<span class="w">    </span><span class="n">m__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__root</span><span class="p">;</span>
+<span class="w">    </span><span class="n">_read</span><span class="p">();</span>
+<span class="p">}</span>
+
+<span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">_read</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">m_cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="p">}</span>
+
+<span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::~</span><span class="n">flags_t</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">_clean_up</span><span class="p">();</span>
+<span class="p">}</span>
+
+<span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">_clean_up</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
 <span class="p">}</span>
 </pre></div>
 
@@ -458,7 +602,7 @@ <h3>tcp_segment.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/cpp_stl_98.html b/tcp_segment/cpp_stl_98.html
index d81a35790..3e83b0e23 100644
--- a/tcp_segment/cpp_stl_98.html
+++ b/tcp_segment/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -316,7 +321,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by invoking getter methods like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -366,6 +371,7 @@ <h3>tcp_segment.h</h3>
 <span class="k">class</span><span class="w"> </span><span class="nc">tcp_segment_t</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">public</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="w"> </span><span class="p">{</span>
 
 <span class="k">public</span><span class="o">:</span>
+<span class="w">    </span><span class="k">class</span><span class="w"> </span><span class="nc">flags_t</span><span class="p">;</span>
 
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">);</span>
 
@@ -376,30 +382,134 @@ <h3>tcp_segment.h</h3>
 <span class="k">public</span><span class="o">:</span>
 <span class="w">    </span><span class="o">~</span><span class="n">tcp_segment_t</span><span class="p">();</span>
 
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="k">class</span><span class="w"> </span><span class="nc">flags_t</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="k">public</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="w"> </span><span class="p">{</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+
+<span class="w">        </span><span class="n">flags_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">);</span>
+
+<span class="w">    </span><span class="k">private</span><span class="o">:</span>
+<span class="w">        </span><span class="kt">void</span><span class="w"> </span><span class="n">_read</span><span class="p">();</span>
+<span class="w">        </span><span class="kt">void</span><span class="w"> </span><span class="nf">_clean_up</span><span class="p">();</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+<span class="w">        </span><span class="o">~</span><span class="n">flags_t</span><span class="p">();</span>
+
+<span class="w">    </span><span class="k">private</span><span class="o">:</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_cwr</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_ece</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_urg</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_ack</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_psh</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_rst</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_syn</span><span class="p">;</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">m_fin</span><span class="p">;</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span>
+
+<span class="w">    </span><span class="k">public</span><span class="o">:</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Congestion Window Reduced</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">cwr</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_cwr</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * ECN-Echo</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">ece</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ece</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Urgent pointer field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">urg</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_urg</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Acknowledgment field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">ack</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ack</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Push function</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">psh</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_psh</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Reset the connection</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">rst</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_rst</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Synchronize sequence numbers</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">syn</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_syn</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * No more data from sender</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kt">bool</span><span class="w"> </span><span class="n">fin</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_fin</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_root</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_parent</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="p">};</span>
+
 <span class="k">private</span><span class="o">:</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_src_port</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_dst_port</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">m_seq_num</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">m_ack_num</span><span class="p">;</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">m_b12</span><span class="p">;</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">m_b13</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">m_data_offset</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">m_reserved</span><span class="p">;</span>
+<span class="w">    </span><span class="n">flags_t</span><span class="o">*</span><span class="w"> </span><span class="n">m_flags</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_window_size</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_checksum</span><span class="p">;</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">m_urgent_pointer</span><span class="p">;</span>
+<span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">m_options</span><span class="p">;</span>
+<span class="w">    </span><span class="kt">bool</span><span class="w"> </span><span class="n">n_options</span><span class="p">;</span>
+
+<span class="k">public</span><span class="o">:</span>
+<span class="w">    </span><span class="kt">bool</span><span class="w"> </span><span class="n">_is_null_options</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="n">options</span><span class="p">();</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">n_options</span><span class="p">;</span><span class="w"> </span><span class="p">};</span>
+
+<span class="k">private</span><span class="o">:</span>
 <span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">m_body</span><span class="p">;</span>
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span>
 <span class="w">    </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span>
 
 <span class="k">public</span><span class="o">:</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Source port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">src_port</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_src_port</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Destination port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">dst_port</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_dst_port</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Sequence number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">seq_num</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_seq_num</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Acknowledgment number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kt">uint32_t</span><span class="w"> </span><span class="n">ack_num</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_ack_num</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">b12</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_b12</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kt">uint8_t</span><span class="w"> </span><span class="n">b13</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_b13</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="cm">     */</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_data_offset</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="kt">uint64_t</span><span class="w"> </span><span class="n">reserved</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_reserved</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="n">flags_t</span><span class="o">*</span><span class="w"> </span><span class="n">flags</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_flags</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">window_size</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_window_size</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">checksum</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_checksum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kt">uint16_t</span><span class="w"> </span><span class="n">urgent_pointer</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_urgent_pointer</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">options</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_options</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">std</span><span class="o">::</span><span class="n">string</span><span class="w"> </span><span class="n">body</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_body</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">_root</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">_parent</span><span class="p">()</span><span class="w"> </span><span class="k">const</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m__parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
@@ -429,6 +539,7 @@ <h3>tcp_segment.cpp</h3>
 <span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">tcp_segment_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="p">)</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="p">(</span><span class="n">p__io</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
 <span class="w">    </span><span class="n">m__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__parent</span><span class="p">;</span>
 <span class="w">    </span><span class="n">m__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">;</span>
+<span class="w">    </span><span class="n">m_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
 
 <span class="w">    </span><span class="k">try</span><span class="w"> </span><span class="p">{</span>
 <span class="w">        </span><span class="n">_read</span><span class="p">();</span>
@@ -443,11 +554,18 @@ <h3>tcp_segment.cpp</h3>
 <span class="w">    </span><span class="n">m_dst_port</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_seq_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_ack_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
-<span class="w">    </span><span class="n">m_b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
-<span class="w">    </span><span class="n">m_b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
+<span class="w">    </span><span class="n">m_data_offset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">align_to_byte</span><span class="p">();</span>
+<span class="w">    </span><span class="n">m_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="n">flags_t</span><span class="p">(</span><span class="n">m__io</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="n">m__root</span><span class="p">);</span>
 <span class="w">    </span><span class="n">m_window_size</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="n">m_urgent_pointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
+<span class="w">    </span><span class="n">n_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nb">true</span><span class="p">;</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="n">n_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nb">false</span><span class="p">;</span>
+<span class="w">        </span><span class="n">m_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bytes</span><span class="p">(((</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">));</span>
+<span class="w">    </span><span class="p">}</span>
 <span class="w">    </span><span class="n">m_body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bytes_full</span><span class="p">();</span>
 <span class="p">}</span>
 
@@ -456,6 +574,41 @@ <h3>tcp_segment.cpp</h3>
 <span class="p">}</span>
 
 <span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">_clean_up</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(</span><span class="n">m_flags</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="k">delete</span><span class="w"> </span><span class="n">m_flags</span><span class="p">;</span><span class="w"> </span><span class="n">m_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">    </span><span class="p">}</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(</span><span class="o">!</span><span class="n">n_options</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="p">}</span>
+<span class="p">}</span>
+
+<span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">flags_t</span><span class="p">(</span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstream</span><span class="o">*</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__parent</span><span class="p">,</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">*</span><span class="w"> </span><span class="n">p__root</span><span class="p">)</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="n">kaitai</span><span class="o">::</span><span class="n">kstruct</span><span class="p">(</span><span class="n">p__io</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">m__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__parent</span><span class="p">;</span>
+<span class="w">    </span><span class="n">m__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__root</span><span class="p">;</span>
+
+<span class="w">    </span><span class="k">try</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="n">_read</span><span class="p">();</span>
+<span class="w">    </span><span class="p">}</span><span class="w"> </span><span class="k">catch</span><span class="p">(...)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="n">_clean_up</span><span class="p">();</span>
+<span class="w">        </span><span class="k">throw</span><span class="p">;</span>
+<span class="w">    </span><span class="p">}</span>
+<span class="p">}</span>
+
+<span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">_read</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">m_cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="n">m_fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m__io</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="p">}</span>
+
+<span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::~</span><span class="n">flags_t</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="n">_clean_up</span><span class="p">();</span>
+<span class="p">}</span>
+
+<span class="kt">void</span><span class="w"> </span><span class="n">tcp_segment_t</span><span class="o">::</span><span class="n">flags_t</span><span class="o">::</span><span class="n">_clean_up</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
 <span class="p">}</span>
 </pre></div>
 
@@ -466,7 +619,7 @@ <h3>tcp_segment.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/csharp.html b/tcp_segment/csharp.html
index 3263d955f..a731e9862 100644
--- a/tcp_segment/csharp.html
+++ b/tcp_segment/csharp.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -279,7 +284,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by accessing properties like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">SrcPort</span><span class="w"> </span><span class="c1">// =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="n">SrcPort</span><span class="w"> </span><span class="c1">// =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -339,34 +344,144 @@ <h3>TcpSegment.cs</h3>
 <span class="w">            </span><span class="n">_dstPort</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU2be</span><span class="p">();</span>
 <span class="w">            </span><span class="n">_seqNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU4be</span><span class="p">();</span>
 <span class="w">            </span><span class="n">_ackNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU4be</span><span class="p">();</span>
-<span class="w">            </span><span class="n">_b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU1</span><span class="p">();</span>
-<span class="w">            </span><span class="n">_b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU1</span><span class="p">();</span>
+<span class="w">            </span><span class="n">_dataOffset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">4</span><span class="p">);</span>
+<span class="w">            </span><span class="n">_reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">4</span><span class="p">);</span>
+<span class="w">            </span><span class="n">m_io</span><span class="p">.</span><span class="n">AlignToByte</span><span class="p">();</span>
+<span class="w">            </span><span class="n">_flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="n">Flags</span><span class="p">(</span><span class="n">m_io</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="n">m_root</span><span class="p">);</span>
 <span class="w">            </span><span class="n">_windowSize</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU2be</span><span class="p">();</span>
 <span class="w">            </span><span class="n">_checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU2be</span><span class="p">();</span>
 <span class="w">            </span><span class="n">_urgentPointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadU2be</span><span class="p">();</span>
+<span class="w">            </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="n">DataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="m">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="m">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">                </span><span class="n">_options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBytes</span><span class="p">(((</span><span class="n">DataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="m">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="m">20</span><span class="p">));</span>
+<span class="w">            </span><span class="p">}</span>
 <span class="w">            </span><span class="n">_body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBytesFull</span><span class="p">();</span>
 <span class="w">        </span><span class="p">}</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// TCP header flags as defined &amp;quot;TCP Header Flags&amp;quot; registry.</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="k">partial</span><span class="w"> </span><span class="k">class</span><span class="w"> </span><span class="nc">Flags</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="n">KaitaiStruct</span>
+<span class="w">        </span><span class="p">{</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="k">static</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="nf">FromFile</span><span class="p">(</span><span class="kt">string</span><span class="w"> </span><span class="n">fileName</span><span class="p">)</span>
+<span class="w">            </span><span class="p">{</span>
+<span class="w">                </span><span class="k">return</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="nf">Flags</span><span class="p">(</span><span class="k">new</span><span class="w"> </span><span class="n">KaitaiStream</span><span class="p">(</span><span class="n">fileName</span><span class="p">));</span>
+<span class="w">            </span><span class="p">}</span>
+
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="nf">Flags</span><span class="p">(</span><span class="n">KaitaiStream</span><span class="w"> </span><span class="n">p__io</span><span class="p">,</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">p__parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">null</span><span class="p">,</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">p__root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">null</span><span class="p">)</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="k">base</span><span class="p">(</span><span class="n">p__io</span><span class="p">)</span>
+<span class="w">            </span><span class="p">{</span>
+<span class="w">                </span><span class="n">m_parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__parent</span><span class="p">;</span>
+<span class="w">                </span><span class="n">m_root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">p__root</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_read</span><span class="p">();</span>
+<span class="w">            </span><span class="p">}</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="k">void</span><span class="w"> </span><span class="nf">_read</span><span class="p">()</span>
+<span class="w">            </span><span class="p">{</span>
+<span class="w">                </span><span class="n">_cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">                </span><span class="n">_fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">m_io</span><span class="p">.</span><span class="n">ReadBitsIntBe</span><span class="p">(</span><span class="m">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="m">0</span><span class="p">;</span>
+<span class="w">            </span><span class="p">}</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_cwr</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_ece</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_urg</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_ack</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_psh</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_rst</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_syn</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">_fin</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">m_root</span><span class="p">;</span>
+<span class="w">            </span><span class="k">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">m_parent</span><span class="p">;</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Congestion Window Reduced</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Cwr</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_cwr</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// ECN-Echo</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Ece</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_ece</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Urgent pointer field is significant</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Urg</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_urg</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Acknowledgment field is significant</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Ack</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_ack</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Push function</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Psh</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_psh</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Reset the connection</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Rst</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_rst</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// Synchronize sequence numbers</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Syn</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_syn</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">            </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">            </span><span class="c1">/// No more data from sender</span>
+<span class="w">            </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="kt">bool</span><span class="w"> </span><span class="n">Fin</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_fin</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">M_Root</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">            </span><span class="k">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">M_Parent</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="p">}</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">_srcPort</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">_dstPort</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">uint</span><span class="w"> </span><span class="n">_seqNum</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">uint</span><span class="w"> </span><span class="n">_ackNum</span><span class="p">;</span>
-<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">byte</span><span class="w"> </span><span class="n">_b12</span><span class="p">;</span>
-<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">byte</span><span class="w"> </span><span class="n">_b13</span><span class="p">;</span>
+<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ulong</span><span class="w"> </span><span class="n">_dataOffset</span><span class="p">;</span>
+<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ulong</span><span class="w"> </span><span class="n">_reserved</span><span class="p">;</span>
+<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="n">_flags</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">_windowSize</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">_checksum</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">_urgentPointer</span><span class="p">;</span>
+<span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">byte</span><span class="p">[]</span><span class="w"> </span><span class="n">_options</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="kt">byte</span><span class="p">[]</span><span class="w"> </span><span class="n">_body</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">m_root</span><span class="p">;</span>
 <span class="w">        </span><span class="k">private</span><span class="w"> </span><span class="n">KaitaiStruct</span><span class="w"> </span><span class="n">m_parent</span><span class="p">;</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// Source port</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">SrcPort</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_srcPort</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// Destination port</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">DstPort</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_dstPort</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// Sequence number</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">uint</span><span class="w"> </span><span class="n">SeqNum</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_seqNum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// Acknowledgment number</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">uint</span><span class="w"> </span><span class="n">AckNum</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_ackNum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
-<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">byte</span><span class="w"> </span><span class="n">B12</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_b12</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
-<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">byte</span><span class="w"> </span><span class="n">B13</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_b13</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="c1">/// &lt;summary&gt;</span>
+<span class="w">        </span><span class="c1">/// Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="w">        </span><span class="c1">/// &lt;/summary&gt;</span>
+<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ulong</span><span class="w"> </span><span class="n">DataOffset</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_dataOffset</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ulong</span><span class="w"> </span><span class="n">Reserved</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_reserved</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_flags</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">WindowSize</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_windowSize</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">Checksum</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_checksum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">ushort</span><span class="w"> </span><span class="n">UrgentPointer</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_urgentPointer</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">byte</span><span class="p">[]</span><span class="w"> </span><span class="n">Options</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_options</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="kt">byte</span><span class="p">[]</span><span class="w"> </span><span class="n">Body</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_body</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">M_Root</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
 <span class="w">        </span><span class="k">public</span><span class="w"> </span><span class="n">KaitaiStruct</span><span class="w"> </span><span class="n">M_Parent</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">get</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">m_parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span><span class="w"> </span><span class="p">}</span>
@@ -381,7 +496,7 @@ <h3>TcpSegment.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/go.html b/tcp_segment/go.html
index c2176deda..69a503a5e 100644
--- a/tcp_segment/go.html
+++ b/tcp_segment/go.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -281,11 +286,13 @@ <h3>tcp_segment.go</h3>
 <span class="w">	</span><span class="nx">DstPort</span><span class="w"> </span><span class="kt">uint16</span>
 <span class="w">	</span><span class="nx">SeqNum</span><span class="w"> </span><span class="kt">uint32</span>
 <span class="w">	</span><span class="nx">AckNum</span><span class="w"> </span><span class="kt">uint32</span>
-<span class="w">	</span><span class="nx">B12</span><span class="w"> </span><span class="kt">uint8</span>
-<span class="w">	</span><span class="nx">B13</span><span class="w"> </span><span class="kt">uint8</span>
+<span class="w">	</span><span class="nx">DataOffset</span><span class="w"> </span><span class="kt">uint64</span>
+<span class="w">	</span><span class="nx">Reserved</span><span class="w"> </span><span class="kt">uint64</span>
+<span class="w">	</span><span class="nx">Flags</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment_Flags</span>
 <span class="w">	</span><span class="nx">WindowSize</span><span class="w"> </span><span class="kt">uint16</span>
 <span class="w">	</span><span class="nx">Checksum</span><span class="w"> </span><span class="kt">uint16</span>
 <span class="w">	</span><span class="nx">UrgentPointer</span><span class="w"> </span><span class="kt">uint16</span>
+<span class="w">	</span><span class="nx">Options</span><span class="w"> </span><span class="p">[]</span><span class="kt">byte</span>
 <span class="w">	</span><span class="nx">Body</span><span class="w"> </span><span class="p">[]</span><span class="kt">byte</span>
 <span class="w">	</span><span class="nx">_io</span><span class="w"> </span><span class="o">*</span><span class="nx">kaitai</span><span class="p">.</span><span class="nx">Stream</span>
 <span class="w">	</span><span class="nx">_root</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment</span>
@@ -321,39 +328,175 @@ <h3>tcp_segment.go</h3>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
 <span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">AckNum</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint32</span><span class="p">(</span><span class="nx">tmp4</span><span class="p">)</span>
-<span class="w">	</span><span class="nx">tmp5</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU1</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">tmp5</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">B12</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp5</span>
-<span class="w">	</span><span class="nx">tmp6</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU1</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">DataOffset</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp5</span>
+<span class="w">	</span><span class="nx">tmp6</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">B13</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp6</span>
-<span class="w">	</span><span class="nx">tmp7</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU2be</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Reserved</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp6</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">AlignToByte</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">tmp7</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">NewTcpSegment_Flags</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">err</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp7</span><span class="p">.</span><span class="nx">Read</span><span class="p">(</span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">,</span><span class="w"> </span><span class="nx">this</span><span class="p">,</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_root</span><span class="p">)</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">WindowSize</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp7</span><span class="p">)</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Flags</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp7</span>
 <span class="w">	</span><span class="nx">tmp8</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU2be</span><span class="p">()</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Checksum</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp8</span><span class="p">)</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">WindowSize</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp8</span><span class="p">)</span>
 <span class="w">	</span><span class="nx">tmp9</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU2be</span><span class="p">()</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">UrgentPointer</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp9</span><span class="p">)</span>
-<span class="w">	</span><span class="nx">tmp10</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBytesFull</span><span class="p">()</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Checksum</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp9</span><span class="p">)</span>
+<span class="w">	</span><span class="nx">tmp10</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadU2be</span><span class="p">()</span>
 <span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
 <span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="w">	</span><span class="p">}</span>
-<span class="w">	</span><span class="nx">tmp10</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp10</span>
-<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Body</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp10</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">UrgentPointer</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nb">uint16</span><span class="p">(</span><span class="nx">tmp10</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="nx">this</span><span class="p">.</span><span class="nx">DataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="nx">tmp11</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBytes</span><span class="p">(</span><span class="nb">int</span><span class="p">(((</span><span class="nx">this</span><span class="p">.</span><span class="nx">DataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)))</span>
+<span class="w">		</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">			</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">		</span><span class="p">}</span>
+<span class="w">		</span><span class="nx">tmp11</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp11</span>
+<span class="w">		</span><span class="nx">this</span><span class="p">.</span><span class="nx">Options</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp11</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">tmp12</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBytesFull</span><span class="p">()</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">tmp12</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp12</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Body</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp12</span>
 <span class="w">	</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
 <span class="p">}</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Source port</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Destination port</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Sequence number</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Acknowledgment number</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="cm"> */</span>
+<span class="kd">type</span><span class="w"> </span><span class="nx">TcpSegment_Flags</span><span class="w"> </span><span class="kd">struct</span><span class="w"> </span><span class="p">{</span>
+<span class="w">	</span><span class="nx">Cwr</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Ece</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Urg</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Ack</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Psh</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Rst</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Syn</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">Fin</span><span class="w"> </span><span class="kt">bool</span>
+<span class="w">	</span><span class="nx">_io</span><span class="w"> </span><span class="o">*</span><span class="nx">kaitai</span><span class="p">.</span><span class="nx">Stream</span>
+<span class="w">	</span><span class="nx">_root</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment</span>
+<span class="w">	</span><span class="nx">_parent</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment</span>
+<span class="p">}</span>
+<span class="kd">func</span><span class="w"> </span><span class="nx">NewTcpSegment_Flags</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment_Flags</span><span class="w"> </span><span class="p">{</span>
+<span class="w">	</span><span class="k">return</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">TcpSegment_Flags</span><span class="p">{</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="p">}</span>
+
+<span class="kd">func</span><span class="w"> </span><span class="p">(</span><span class="nx">this</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment_Flags</span><span class="p">)</span><span class="w"> </span><span class="nx">Read</span><span class="p">(</span><span class="nx">io</span><span class="w"> </span><span class="o">*</span><span class="nx">kaitai</span><span class="p">.</span><span class="nx">Stream</span><span class="p">,</span><span class="w"> </span><span class="nx">parent</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment</span><span class="p">,</span><span class="w"> </span><span class="nx">root</span><span class="w"> </span><span class="o">*</span><span class="nx">TcpSegment</span><span class="p">)</span><span class="w"> </span><span class="p">(</span><span class="nx">err</span><span class="w"> </span><span class="kt">error</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">io</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">_parent</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">parent</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">_root</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">root</span>
+
+<span class="w">	</span><span class="nx">tmp13</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Cwr</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp13</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp14</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Ece</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp14</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp15</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Urg</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp15</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp16</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Ack</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp16</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp17</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Psh</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp17</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp18</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Rst</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp18</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp19</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Syn</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp19</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="nx">tmp20</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">ReadBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span>
+<span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span>
+<span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nx">this</span><span class="p">.</span><span class="nx">Fin</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">tmp20</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">	</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span>
+<span class="p">}</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Congestion Window Reduced</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * ECN-Echo</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Urgent pointer field is significant</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Acknowledgment field is significant</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Push function</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Reset the connection</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * Synchronize sequence numbers</span>
+<span class="cm"> */</span>
+
+<span class="cm">/**</span>
+<span class="cm"> * No more data from sender</span>
+<span class="cm"> */</span>
 </pre></div>
 
         </div>
@@ -363,7 +506,7 @@ <h3>tcp_segment.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/graphviz.html b/tcp_segment/graphviz.html
index eb8fe51c5..e2558e2c5 100644
--- a/tcp_segment/graphviz.html
+++ b/tcp_segment/graphviz.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -278,14 +283,34 @@ <h3>tcp_segment.dot</h3>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;dst_port_pos&quot;</span><span class="p">&gt;</span><span class="nt">2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;dst_port_size&quot;</span><span class="p">&gt;</span><span class="nt">2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u2be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;dst_port_type&quot;</span><span class="p">&gt;</span><span class="nt">dst_port</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;seq_num_pos&quot;</span><span class="p">&gt;</span><span class="nt">4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;seq_num_size&quot;</span><span class="p">&gt;</span><span class="nt">4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u4be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;seq_num_type&quot;</span><span class="p">&gt;</span><span class="nt">seq_num</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_num_pos&quot;</span><span class="p">&gt;</span><span class="nt">8</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_num_size&quot;</span><span class="p">&gt;</span><span class="nt">4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u4be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_num_type&quot;</span><span class="p">&gt;</span><span class="nt">ack_num</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
-<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b12_pos&quot;</span><span class="p">&gt;</span><span class="nt">12</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b12_size&quot;</span><span class="p">&gt;</span><span class="nt">1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b12_type&quot;</span><span class="p">&gt;</span><span class="nt">b12</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
-<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b13_pos&quot;</span><span class="p">&gt;</span><span class="nt">13</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b13_size&quot;</span><span class="p">&gt;</span><span class="nt">1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;b13_type&quot;</span><span class="p">&gt;</span><span class="nt">b13</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;data_offset_pos&quot;</span><span class="p">&gt;</span><span class="nt">12</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;data_offset_size&quot;</span><span class="p">&gt;</span><span class="nt">4b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">b4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;data_offset_type&quot;</span><span class="p">&gt;</span><span class="nt">data_offset</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;reserved_pos&quot;</span><span class="p">&gt;</span><span class="nt">12:4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;reserved_size&quot;</span><span class="p">&gt;</span><span class="nt">4b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">b4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;reserved_type&quot;</span><span class="p">&gt;</span><span class="nt">reserved</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;flags_pos&quot;</span><span class="p">&gt;</span><span class="nt">13</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;flags_size&quot;</span><span class="p">&gt;</span><span class="nt">1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">Flags</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;flags_type&quot;</span><span class="p">&gt;</span><span class="nt">flags</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;window_size_pos&quot;</span><span class="p">&gt;</span><span class="nt">14</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;window_size_size&quot;</span><span class="p">&gt;</span><span class="nt">2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u2be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;window_size_type&quot;</span><span class="p">&gt;</span><span class="nt">window_size</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;checksum_pos&quot;</span><span class="p">&gt;</span><span class="nt">16</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;checksum_size&quot;</span><span class="p">&gt;</span><span class="nt">2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u2be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;checksum_type&quot;</span><span class="p">&gt;</span><span class="nt">checksum</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urgent_pointer_pos&quot;</span><span class="p">&gt;</span><span class="nt">18</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urgent_pointer_size&quot;</span><span class="p">&gt;</span><span class="nt">2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">u2be</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urgent_pointer_type&quot;</span><span class="p">&gt;</span><span class="nt">urgent_pointer</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
-<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_pos&quot;</span><span class="p">&gt;</span><span class="nt">20</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_size&quot;</span><span class="p">&gt;</span><span class="nt">⇲</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_type&quot;</span><span class="p">&gt;</span><span class="nt">body</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;options_pos&quot;</span><span class="p">&gt;</span><span class="nt">20</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;options_size&quot;</span><span class="p">&gt;</span><span class="nt">((data_offset</span><span class="w"> </span><span class="nt">*</span><span class="w"> </span><span class="nt">4)</span><span class="w"> </span><span class="nt">-</span><span class="w"> </span><span class="nt">20)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;options_type&quot;</span><span class="p">&gt;</span><span class="nt">options</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_pos&quot;</span><span class="p">&gt;</span><span class="nt">...</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_size&quot;</span><span class="p">&gt;</span><span class="nt">⇲</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;body_type&quot;</span><span class="p">&gt;</span><span class="nt">body</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
 <span class="w">		</span><span class="p">&lt;</span><span class="nt">/TABLE</span><span class="p">&gt;&gt;];</span>
+<span class="w">		</span><span class="k">subgraph</span><span class="w"> </span><span class="nt">cluster__flags</span><span class="w"> </span><span class="p">{</span>
+<span class="w">			</span><span class="na">label</span><span class="p">=</span><span class="s2">&quot;TcpSegment::Flags&quot;</span><span class="p">;</span>
+<span class="w">			</span><span class="k">graph</span><span class="p">[</span><span class="na">style</span><span class="p">=</span><span class="s">dotted</span><span class="p">];</span>
+
+<span class="w">			</span><span class="nt">flags__seq</span><span class="w"> </span><span class="p">[</span><span class="na">label</span><span class="p">=&lt;&lt;</span><span class="nt">TABLE</span><span class="w"> </span><span class="nt">BORDER=&quot;0&quot;</span><span class="w"> </span><span class="nt">CELLBORDER=&quot;1&quot;</span><span class="w"> </span><span class="nt">CELLSPACING=&quot;0&quot;</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">BGCOLOR=&quot;#E0FFE0&quot;</span><span class="p">&gt;</span><span class="nt">pos</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">BGCOLOR=&quot;#E0FFE0&quot;</span><span class="p">&gt;</span><span class="nt">size</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">BGCOLOR=&quot;#E0FFE0&quot;</span><span class="p">&gt;</span><span class="nt">type</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">BGCOLOR=&quot;#E0FFE0&quot;</span><span class="p">&gt;</span><span class="nt">id</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;cwr_pos&quot;</span><span class="p">&gt;</span><span class="nt">0</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;cwr_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;cwr_type&quot;</span><span class="p">&gt;</span><span class="nt">cwr</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ece_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:1</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ece_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ece_type&quot;</span><span class="p">&gt;</span><span class="nt">ece</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urg_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:2</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urg_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;urg_type&quot;</span><span class="p">&gt;</span><span class="nt">urg</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:3</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;ack_type&quot;</span><span class="p">&gt;</span><span class="nt">ack</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;psh_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:4</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;psh_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;psh_type&quot;</span><span class="p">&gt;</span><span class="nt">psh</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;rst_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:5</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;rst_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;rst_type&quot;</span><span class="p">&gt;</span><span class="nt">rst</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;syn_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:6</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;syn_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;syn_type&quot;</span><span class="p">&gt;</span><span class="nt">syn</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">				</span><span class="p">&lt;</span><span class="nt">TR</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;fin_pos&quot;</span><span class="p">&gt;</span><span class="nt">0:7</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;fin_size&quot;</span><span class="p">&gt;</span><span class="nt">1b</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="p">&gt;</span><span class="nt">BitsType1(BigBitEndian)</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">TD</span><span class="w"> </span><span class="nt">PORT=&quot;fin_type&quot;</span><span class="p">&gt;</span><span class="nt">fin</span><span class="p">&lt;</span><span class="nt">/TD</span><span class="p">&gt;&lt;</span><span class="nt">/TR</span><span class="p">&gt;</span>
+<span class="w">			</span><span class="p">&lt;</span><span class="nt">/TABLE</span><span class="p">&gt;&gt;];</span>
+<span class="w">		</span><span class="p">}</span>
 <span class="w">	</span><span class="p">}</span>
+<span class="w">	</span><span class="nt">tcp_segment__seq</span><span class="p">:</span><span class="nt">flags_type</span><span class="w"> </span><span class="o">-&gt;</span><span class="w"> </span><span class="nt">flags__seq</span><span class="w"> </span><span class="p">[</span><span class="na">style</span><span class="p">=</span><span class="s">bold</span><span class="p">];</span>
+<span class="w">	</span><span class="nt">tcp_segment__seq</span><span class="p">:</span><span class="nt">data_offset_type</span><span class="w"> </span><span class="o">-&gt;</span><span class="w"> </span><span class="nt">tcp_segment__seq</span><span class="p">:</span><span class="nt">options_size</span><span class="w"> </span><span class="p">[</span><span class="na">color</span><span class="p">=</span><span class="s2">&quot;#404040&quot;</span><span class="p">];</span>
 <span class="p">}</span>
 </pre></div>
 
@@ -296,7 +321,7 @@ <h3>tcp_segment.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/index.html b/tcp_segment/index.html
index 8e70d0987..790046854 100644
--- a/tcp_segment/index.html
+++ b/tcp_segment/index.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -262,9 +267,11 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 <span class="w">    </span><span class="nt">rfc</span><span class="p">:</span>
 <span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">793</span>
 <span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1323</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">9293</span>
 <span class="w">    </span><span class="nt">wikidata</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Q8803</span>
 <span class="w">  </span><span class="nt">license</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">CC0-1.0</span>
 <span class="w">  </span><span class="nt">endian</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">be</span>
+<span class="w">  </span><span class="nt">ks-version</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">0.10</span>
 <span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">|</span>
 <span class="w">  </span><span class="no">TCP is one of the core Internet protocols on transport layer (AKA</span>
 <span class="w">  </span><span class="no">OSI layer 4), providing stateful connections with error checking,</span>
@@ -273,31 +280,79 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 <span class="nt">seq</span><span class="p">:</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">src_port</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u2</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Source port</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">dst_port</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u2</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Destination port</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">seq_num</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u4</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Sequence number</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ack_num</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u4</span>
-<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b12</span>
-<span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u1</span>
-<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b13</span>
-<span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u1</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Acknowledgment number</span>
+<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">data_offset</span>
+<span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b4</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">reserved</span>
+<span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b4</span>
+<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">flags</span>
+<span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">flags</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">window_size</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u2</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">checksum</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u2</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">urgent_pointer</span>
 <span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">u2</span>
+<span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">options</span>
+<span class="w">    </span><span class="nt">size</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">(data_offset * 4) - 20</span>
+<span class="w">    </span><span class="nt">if</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">((data_offset * 4) - 20) != 0</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">body</span>
 <span class="w">    </span><span class="nt">size-eos</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
+<span class="nt">types</span><span class="p">:</span>
+<span class="w">  </span><span class="nt">flags</span><span class="p">:</span>
+<span class="w">    </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">|</span>
+<span class="w">      </span><span class="no">TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="w">    </span><span class="nt">seq</span><span class="p">:</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">cwr</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Congestion Window Reduced</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ece</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ECN-Echo</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">urg</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Urgent pointer field is significant</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ack</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Acknowledgment field is significant</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">psh</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Push function</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">rst</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Reset the connection</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">syn</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Synchronize sequence numbers</span>
+<span class="w">      </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">fin</span>
+<span class="w">        </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">b1</span>
+<span class="w">        </span><span class="nt">doc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">No more data from sender</span>
+<span class="w">    </span><span class="nt">to-string</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">|</span>
+<span class="w">      </span><span class="no">(cwr ? &quot;|CWR&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(ece ? &quot;|ECE&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(urg ? &quot;|URG&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(ack ? &quot;|ACK&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(psh ? &quot;|PSH&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(rst ? &quot;|RST&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(syn ? &quot;|SYN&quot; : &quot;&quot;) +</span>
+<span class="w">      </span><span class="no">(fin ? &quot;|FIN&quot; : &quot;&quot;)</span>
 </pre></div>
     </div>
 </section>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/java.html b/tcp_segment/java.html
index 851be2855..da59a5660 100644
--- a/tcp_segment/java.html
+++ b/tcp_segment/java.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -281,7 +286,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by invoking getter methods like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="na">srcPort</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="p">.</span><span class="na">srcPort</span><span class="p">()</span><span class="w"> </span><span class="c1">// =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -347,34 +352,149 @@ <h3>TcpSegment.java</h3>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">dstPort</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU2be</span><span class="p">();</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">seqNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU4be</span><span class="p">();</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">ackNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU4be</span><span class="p">();</span>
-<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU1</span><span class="p">();</span>
-<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU1</span><span class="p">();</span>
+<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">dataOffset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">alignToByte</span><span class="p">();</span>
+<span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="n">Flags</span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="n">_root</span><span class="p">);</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">windowSize</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU2be</span><span class="p">();</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU2be</span><span class="p">();</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">urgentPointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readU2be</span><span class="p">();</span>
+<span class="w">        </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="n">dataOffset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBytes</span><span class="p">(((</span><span class="n">dataOffset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">));</span>
+<span class="w">        </span><span class="p">}</span>
 <span class="w">        </span><span class="k">this</span><span class="p">.</span><span class="na">body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBytesFull</span><span class="p">();</span>
 <span class="w">    </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="cm">     */</span>
+<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kd">static</span><span class="w"> </span><span class="kd">class</span> <span class="nc">Flags</span><span class="w"> </span><span class="kd">extends</span><span class="w"> </span><span class="n">KaitaiStruct</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kd">static</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="nf">fromFile</span><span class="p">(</span><span class="n">String</span><span class="w"> </span><span class="n">fileName</span><span class="p">)</span><span class="w"> </span><span class="kd">throws</span><span class="w"> </span><span class="n">IOException</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="k">return</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="n">Flags</span><span class="p">(</span><span class="k">new</span><span class="w"> </span><span class="n">ByteBufferKaitaiStream</span><span class="p">(</span><span class="n">fileName</span><span class="p">));</span>
+<span class="w">        </span><span class="p">}</span>
+
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="nf">Flags</span><span class="p">(</span><span class="n">KaitaiStream</span><span class="w"> </span><span class="n">_io</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="k">this</span><span class="p">(</span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w"> </span><span class="kc">null</span><span class="p">);</span>
+<span class="w">        </span><span class="p">}</span>
+
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="nf">Flags</span><span class="p">(</span><span class="n">KaitaiStream</span><span class="w"> </span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_parent</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="k">this</span><span class="p">(</span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="n">_parent</span><span class="p">,</span><span class="w"> </span><span class="kc">null</span><span class="p">);</span>
+<span class="w">        </span><span class="p">}</span>
+
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="nf">Flags</span><span class="p">(</span><span class="n">KaitaiStream</span><span class="w"> </span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_parent</span><span class="p">,</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_root</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="kd">super</span><span class="p">(</span><span class="n">_io</span><span class="p">);</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">_parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">_parent</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">_root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">_root</span><span class="p">;</span>
+<span class="w">            </span><span class="n">_read</span><span class="p">();</span>
+<span class="w">        </span><span class="p">}</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">void</span><span class="w"> </span><span class="nf">_read</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">            </span><span class="k">this</span><span class="p">.</span><span class="na">fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">_io</span><span class="p">.</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">;</span>
+<span class="w">        </span><span class="p">}</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">cwr</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">ece</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">urg</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">ack</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">psh</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">rst</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">syn</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="n">fin</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_root</span><span class="p">;</span>
+<span class="w">        </span><span class="kd">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_parent</span><span class="p">;</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Congestion Window Reduced</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">cwr</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">cwr</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * ECN-Echo</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">ece</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">ece</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Urgent pointer field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">urg</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">urg</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Acknowledgment field is significant</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">ack</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">ack</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Push function</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">psh</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">psh</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Reset the connection</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">rst</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">rst</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * Synchronize sequence numbers</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">syn</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">syn</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">        </span><span class="cm">/**</span>
+<span class="cm">         * No more data from sender</span>
+<span class="cm">         */</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="kt">boolean</span><span class="w"> </span><span class="nf">fin</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">fin</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="nf">_root</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">        </span><span class="kd">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="nf">_parent</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">srcPort</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">dstPort</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="n">seqNum</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="n">ackNum</span><span class="p">;</span>
-<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">b12</span><span class="p">;</span>
-<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">b13</span><span class="p">;</span>
+<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="n">dataOffset</span><span class="p">;</span>
+<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="n">reserved</span><span class="p">;</span>
+<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="n">flags</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">windowSize</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">checksum</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="n">urgentPointer</span><span class="p">;</span>
+<span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">byte</span><span class="o">[]</span><span class="w"> </span><span class="n">options</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="kt">byte</span><span class="o">[]</span><span class="w"> </span><span class="n">body</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="n">_root</span><span class="p">;</span>
 <span class="w">    </span><span class="kd">private</span><span class="w"> </span><span class="n">KaitaiStruct</span><span class="w"> </span><span class="n">_parent</span><span class="p">;</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Source port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">srcPort</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">srcPort</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Destination port</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">dstPort</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">dstPort</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Sequence number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="nf">seqNum</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">seqNum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Acknowledgment number</span>
+<span class="cm">     */</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="nf">ackNum</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">ackNum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">b12</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">b12</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
-<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">b13</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">b13</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="cm">     */</span>
+<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="nf">dataOffset</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">dataOffset</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">long</span><span class="w"> </span><span class="nf">reserved</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">reserved</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="n">Flags</span><span class="w"> </span><span class="nf">flags</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">flags</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">windowSize</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">windowSize</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">checksum</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">checksum</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">int</span><span class="w"> </span><span class="nf">urgentPointer</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">urgentPointer</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
+<span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">byte</span><span class="o">[]</span><span class="w"> </span><span class="nf">options</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">options</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="kt">byte</span><span class="o">[]</span><span class="w"> </span><span class="nf">body</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">body</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="n">TcpSegment</span><span class="w"> </span><span class="nf">_root</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_root</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
 <span class="w">    </span><span class="kd">public</span><span class="w"> </span><span class="n">KaitaiStruct</span><span class="w"> </span><span class="nf">_parent</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="n">_parent</span><span class="p">;</span><span class="w"> </span><span class="p">}</span>
@@ -388,7 +508,7 @@ <h3>TcpSegment.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/javascript.html b/tcp_segment/javascript.html
index 8d57e83f1..707ea53dc 100644
--- a/tcp_segment/javascript.html
+++ b/tcp_segment/javascript.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -276,7 +281,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by accessing fields or properties like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="nx">data</span><span class="p">.</span><span class="nx">srcPort</span><span class="w"> </span><span class="c1">// =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="nx">data</span><span class="p">.</span><span class="nx">srcPort</span><span class="w"> </span><span class="c1">// =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -335,14 +340,101 @@ <h3>TcpSegment.js</h3>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">dstPort</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU2be</span><span class="p">();</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">seqNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU4be</span><span class="p">();</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">ackNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU4be</span><span class="p">();</span>
-<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU1</span><span class="p">();</span>
-<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU1</span><span class="p">();</span>
+<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">dataOffset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">4</span><span class="p">);</span>
+<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">4</span><span class="p">);</span>
+<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">alignToByte</span><span class="p">();</span>
+<span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="ow">new</span><span class="w"> </span><span class="nx">Flags</span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">,</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_root</span><span class="p">);</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">windowSize</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU2be</span><span class="p">();</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU2be</span><span class="p">();</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">urgentPointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readU2be</span><span class="p">();</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="k">this</span><span class="p">.</span><span class="nx">dataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mf">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mf">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBytes</span><span class="p">(((</span><span class="k">this</span><span class="p">.</span><span class="nx">dataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mf">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mf">20</span><span class="p">));</span>
+<span class="w">    </span><span class="p">}</span>
 <span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="nx">body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBytesFull</span><span class="p">();</span>
 <span class="w">  </span><span class="p">}</span>
 
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="cm">   */</span>
+
+<span class="w">  </span><span class="kd">var</span><span class="w"> </span><span class="nx">Flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">TcpSegment</span><span class="p">.</span><span class="nx">Flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="p">(</span><span class="kd">function</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="kd">function</span><span class="w"> </span><span class="nx">Flags</span><span class="p">(</span><span class="nx">_io</span><span class="p">,</span><span class="w"> </span><span class="nx">_parent</span><span class="p">,</span><span class="w"> </span><span class="nx">_root</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">_io</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">_parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">_parent</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">_root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nx">_root</span><span class="w"> </span><span class="o">||</span><span class="w"> </span><span class="k">this</span><span class="p">;</span>
+
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">_read</span><span class="p">();</span>
+<span class="w">    </span><span class="p">}</span>
+<span class="w">    </span><span class="nx">Flags</span><span class="p">.</span><span class="nx">prototype</span><span class="p">.</span><span class="nx">_read</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kd">function</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">      </span><span class="k">this</span><span class="p">.</span><span class="nx">fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="nx">_io</span><span class="p">.</span><span class="nx">readBitsIntBe</span><span class="p">(</span><span class="mf">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mf">0</span><span class="p">;</span>
+<span class="w">    </span><span class="p">}</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Congestion Window Reduced</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * ECN-Echo</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Urgent pointer field is significant</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Acknowledgment field is significant</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Push function</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Reset the connection</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * Synchronize sequence numbers</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="cm">/**</span>
+<span class="cm">     * No more data from sender</span>
+<span class="cm">     */</span>
+
+<span class="w">    </span><span class="nx">Flags</span><span class="p">.</span><span class="nx">prototype</span><span class="p">.</span><span class="nx">toString</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kd">function</span><span class="p">()</span><span class="w"> </span><span class="p">{</span>
+<span class="w">      </span><span class="k">return</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">cwr</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|CWR&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">ece</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|ECE&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">urg</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|URG&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">ack</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|ACK&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">psh</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|PSH&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">rst</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|RST&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">syn</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|SYN&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="k">this</span><span class="p">.</span><span class="nx">fin</span><span class="w"> </span><span class="o">?</span><span class="w"> </span><span class="s2">&quot;|FIN&quot;</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">);</span>
+<span class="w">    </span><span class="p">}</span>
+
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nx">Flags</span><span class="p">;</span>
+<span class="w">  </span><span class="p">})();</span>
+
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * Source port</span>
+<span class="cm">   */</span>
+
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * Destination port</span>
+<span class="cm">   */</span>
+
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * Sequence number</span>
+<span class="cm">   */</span>
+
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * Acknowledgment number</span>
+<span class="cm">   */</span>
+
+<span class="w">  </span><span class="cm">/**</span>
+<span class="cm">   * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="cm">   */</span>
+
 <span class="w">  </span><span class="k">return</span><span class="w"> </span><span class="nx">TcpSegment</span><span class="p">;</span>
 <span class="p">})();</span>
 <span class="k">return</span><span class="w"> </span><span class="nx">TcpSegment</span><span class="p">;</span>
@@ -356,7 +448,7 @@ <h3>TcpSegment.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/lua.html b/tcp_segment/lua.html
index 863ad0069..a35ba1262 100644
--- a/tcp_segment/lua.html
+++ b/tcp_segment/lua.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -291,13 +296,68 @@ <h3>tcp_segment.lua</h3>
   <span class="n">self</span><span class="p">.</span><span class="n">dst_port</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u2be</span><span class="p">()</span>
   <span class="n">self</span><span class="p">.</span><span class="n">seq_num</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u4be</span><span class="p">()</span>
   <span class="n">self</span><span class="p">.</span><span class="n">ack_num</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u4be</span><span class="p">()</span>
-  <span class="n">self</span><span class="p">.</span><span class="n">b12</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u1</span><span class="p">()</span>
-  <span class="n">self</span><span class="p">.</span><span class="n">b13</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u1</span><span class="p">()</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">data_offset</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">reserved</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">align_to_byte</span><span class="p">()</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">flags</span> <span class="o">=</span> <span class="n">TcpSegment</span><span class="p">.</span><span class="n">Flags</span><span class="p">(</span><span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">,</span> <span class="n">self</span><span class="p">,</span> <span class="n">self</span><span class="p">.</span><span class="n">_root</span><span class="p">)</span>
   <span class="n">self</span><span class="p">.</span><span class="n">window_size</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u2be</span><span class="p">()</span>
   <span class="n">self</span><span class="p">.</span><span class="n">checksum</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u2be</span><span class="p">()</span>
   <span class="n">self</span><span class="p">.</span><span class="n">urgent_pointer</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_u2be</span><span class="p">()</span>
+  <span class="kr">if</span> <span class="p">((</span><span class="n">self</span><span class="p">.</span><span class="n">data_offset</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span> <span class="kr">then</span>
+    <span class="n">self</span><span class="p">.</span><span class="n">options</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bytes</span><span class="p">(((</span><span class="n">self</span><span class="p">.</span><span class="n">data_offset</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">))</span>
+  <span class="kr">end</span>
   <span class="n">self</span><span class="p">.</span><span class="n">body</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bytes_full</span><span class="p">()</span>
 <span class="kr">end</span>
+
+<span class="c1">-- </span>
+<span class="c1">-- Source port.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Destination port.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Sequence number.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Acknowledgment number.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present).</span>
+
+<span class="c1">-- </span>
+<span class="c1">-- TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="n">TcpSegment</span><span class="p">.</span><span class="n">Flags</span> <span class="o">=</span> <span class="n">class</span><span class="p">.</span><span class="n">class</span><span class="p">(</span><span class="n">KaitaiStruct</span><span class="p">)</span>
+
+<span class="kr">function</span> <span class="nc">TcpSegment</span><span class="p">.</span><span class="nc">Flags</span><span class="p">:</span><span class="nf">_init</span><span class="p">(</span><span class="n">io</span><span class="p">,</span> <span class="n">parent</span><span class="p">,</span> <span class="n">root</span><span class="p">)</span>
+  <span class="n">KaitaiStruct</span><span class="p">.</span><span class="n">_init</span><span class="p">(</span><span class="n">self</span><span class="p">,</span> <span class="n">io</span><span class="p">)</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">_parent</span> <span class="o">=</span> <span class="n">parent</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">_root</span> <span class="o">=</span> <span class="n">root</span> <span class="ow">or</span> <span class="n">self</span>
+  <span class="n">self</span><span class="p">:</span><span class="n">_read</span><span class="p">()</span>
+<span class="kr">end</span>
+
+<span class="kr">function</span> <span class="nc">TcpSegment</span><span class="p">.</span><span class="nc">Flags</span><span class="p">:</span><span class="nf">_read</span><span class="p">()</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">cwr</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">ece</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">urg</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">ack</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">psh</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">rst</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">syn</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+  <span class="n">self</span><span class="p">.</span><span class="n">fin</span> <span class="o">=</span> <span class="n">self</span><span class="p">.</span><span class="n">_io</span><span class="p">:</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">~=</span> <span class="mi">0</span>
+<span class="kr">end</span>
+
+<span class="c1">-- </span>
+<span class="c1">-- Congestion Window Reduced.</span>
+<span class="c1">-- </span>
+<span class="c1">-- ECN-Echo.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Urgent pointer field is significant.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Acknowledgment field is significant.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Push function.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Reset the connection.</span>
+<span class="c1">-- </span>
+<span class="c1">-- Synchronize sequence numbers.</span>
+<span class="c1">-- </span>
+<span class="c1">-- No more data from sender.</span>
 </pre></div>
 
         </div>
@@ -307,7 +367,7 @@ <h3>tcp_segment.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/nim.html b/tcp_segment/nim.html
index 577cf441b..41238d8af 100644
--- a/tcp_segment/nim.html
+++ b/tcp_segment/nim.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -274,15 +279,28 @@ <h3>tcp_segment.nim</h3>
 <span class="w">    </span><span class="p">`</span><span class="n">dstPort</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint16</span>
 <span class="w">    </span><span class="p">`</span><span class="n">seqNum</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint32</span>
 <span class="w">    </span><span class="p">`</span><span class="n">ackNum</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint32</span>
-<span class="w">    </span><span class="p">`</span><span class="n">b12</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint8</span>
-<span class="w">    </span><span class="p">`</span><span class="n">b13</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint8</span>
+<span class="w">    </span><span class="p">`</span><span class="n">dataOffset</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint64</span>
+<span class="w">    </span><span class="p">`</span><span class="n">reserved</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint64</span>
+<span class="w">    </span><span class="p">`</span><span class="n">flags</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">TcpSegment_Flags</span>
 <span class="w">    </span><span class="p">`</span><span class="n">windowSize</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint16</span>
 <span class="w">    </span><span class="p">`</span><span class="n">checksum</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint16</span>
 <span class="w">    </span><span class="p">`</span><span class="n">urgentPointer</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">uint16</span>
+<span class="w">    </span><span class="p">`</span><span class="n">options</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">seq</span><span class="o">[</span><span class="n">byte</span><span class="o">]</span>
 <span class="w">    </span><span class="p">`</span><span class="n">body</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">seq</span><span class="o">[</span><span class="n">byte</span><span class="o">]</span>
 <span class="w">    </span><span class="p">`</span><span class="n">parent</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">KaitaiStruct</span>
+<span class="w">  </span><span class="n">TcpSegment_Flags</span><span class="o">*</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">ref</span><span class="w"> </span><span class="k">object</span><span class="w"> </span><span class="k">of</span><span class="w"> </span><span class="n">KaitaiStruct</span>
+<span class="w">    </span><span class="p">`</span><span class="n">cwr</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">ece</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">urg</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">ack</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">psh</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">rst</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">syn</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">fin</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="nb">bool</span>
+<span class="w">    </span><span class="p">`</span><span class="n">parent</span><span class="p">`</span><span class="o">*</span><span class="p">:</span><span class="w"> </span><span class="n">TcpSegment</span>
 
 <span class="k">proc</span><span class="w"> </span><span class="nf">read</span><span class="o">*</span><span class="p">(</span><span class="err">_: typedesc[TcpSegment], io: KaitaiStream, root: KaitaiStruct, parent: KaitaiStruct): TcpSegment</span>
+<span class="k">proc</span><span class="w"> </span><span class="nf">read</span><span class="o">*</span><span class="p">(</span><span class="err">_: typedesc[TcpSegment_Flags], io: KaitaiStream, root: KaitaiStruct, parent: TcpSegment): TcpSegment_Flags</span>
 
 
 
@@ -301,29 +319,120 @@ <h3>tcp_segment.nim</h3>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">root</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">parent</span>
 
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Source port</span>
+<span class="sd">  ]##</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">srcPortExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU2be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">srcPort</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">srcPortExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Destination port</span>
+<span class="sd">  ]##</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">dstPortExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU2be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">dstPort</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">dstPortExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Sequence number</span>
+<span class="sd">  ]##</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">seqNumExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU4be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">seqNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">seqNumExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Acknowledgment number</span>
+<span class="sd">  ]##</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">ackNumExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU4be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">ackNum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">ackNumExpr</span>
-<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">b12Expr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU1</span><span class="p">()</span>
-<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">b12Expr</span>
-<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">b13Expr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU1</span><span class="p">()</span>
-<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">b13Expr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">dataOffsetExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">dataOffset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">dataOffsetExpr</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">reservedExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">reservedExpr</span>
+<span class="w">  </span><span class="n">alignToByte</span><span class="p">(</span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">)</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">flagsExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">TcpSegment_Flags</span><span class="p">.</span><span class="n">read</span><span class="p">(</span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">,</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">root</span><span class="p">,</span><span class="w"> </span><span class="n">this</span><span class="p">)</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">flagsExpr</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">windowSizeExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU2be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">windowSize</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">windowSizeExpr</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">checksumExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU2be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">checksumExpr</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">urgentPointerExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readU2be</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">urgentPointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">urgentPointerExpr</span>
+<span class="w">  </span><span class="k">if</span><span class="w"> </span><span class="p">((</span><span class="n">this</span><span class="p">.</span><span class="n">dataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">:</span>
+<span class="w">    </span><span class="k">let</span><span class="w"> </span><span class="n">optionsExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBytes</span><span class="p">(</span><span class="nb">int</span><span class="p">(((</span><span class="n">this</span><span class="p">.</span><span class="n">dataOffset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)))</span>
+<span class="w">    </span><span class="n">this</span><span class="p">.</span><span class="n">options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">optionsExpr</span>
 <span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">bodyExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBytesFull</span><span class="p">()</span>
 <span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">bodyExpr</span>
 
 <span class="k">proc</span><span class="w"> </span><span class="nf">fromFile</span><span class="o">*</span><span class="p">(</span><span class="err">_: typedesc[TcpSegment], filename: string): TcpSegment =</span>
 <span class="w">  </span><span class="n">TcpSegment</span><span class="p">.</span><span class="n">read</span><span class="p">(</span><span class="n">newKaitaiFileStream</span><span class="p">(</span><span class="n">filename</span><span class="p">),</span><span class="w"> </span><span class="kp">nil</span><span class="p">,</span><span class="w"> </span><span class="kp">nil</span><span class="p">)</span>
+
+
+<span class="sd">##[</span>
+<span class="sd">TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+
+<span class="sd">]##</span>
+<span class="k">proc</span><span class="w"> </span><span class="nf">read</span><span class="o">*</span><span class="p">(</span><span class="err">_: typedesc[TcpSegment_Flags], io: KaitaiStream, root: KaitaiStruct, parent: TcpSegment): TcpSegment_Flags =</span>
+<span class="w">  </span><span class="k">template</span><span class="w"> </span><span class="nf">this</span><span class="p">:</span><span class="w"> </span><span class="n">untyped</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">result</span>
+<span class="w">  </span><span class="n">this</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">new</span><span class="p">(</span><span class="n">TcpSegment_Flags</span><span class="p">)</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">if</span><span class="w"> </span><span class="n">root</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="kp">nil</span><span class="p">:</span><span class="w"> </span><span class="k">cast</span><span class="o">[</span><span class="n">TcpSegment</span><span class="o">]</span><span class="p">(</span><span class="n">this</span><span class="p">)</span><span class="w"> </span><span class="k">else</span><span class="p">:</span><span class="w"> </span><span class="k">cast</span><span class="o">[</span><span class="n">TcpSegment</span><span class="o">]</span><span class="p">(</span><span class="n">root</span><span class="p">)</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">io</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">root</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">parent</span>
+
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Congestion Window Reduced</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">cwrExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">cwrExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  ECN-Echo</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">eceExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">eceExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Urgent pointer field is significant</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">urgExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">urgExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Acknowledgment field is significant</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">ackExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">ackExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Push function</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">pshExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">pshExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Reset the connection</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">rstExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">rstExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  Synchronize sequence numbers</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">synExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">synExpr</span>
+
+<span class="w">  </span><span class="sd">##[</span>
+<span class="sd">  No more data from sender</span>
+<span class="sd">  ]##</span>
+<span class="w">  </span><span class="k">let</span><span class="w"> </span><span class="n">finExpr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">this</span><span class="p">.</span><span class="n">io</span><span class="p">.</span><span class="n">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">  </span><span class="n">this</span><span class="p">.</span><span class="n">fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">finExpr</span>
+
+<span class="k">proc</span><span class="w"> </span><span class="nf">fromFile</span><span class="o">*</span><span class="p">(</span><span class="err">_: typedesc[TcpSegment_Flags], filename: string): TcpSegment_Flags =</span>
+<span class="w">  </span><span class="n">TcpSegment_Flags</span><span class="p">.</span><span class="n">read</span><span class="p">(</span><span class="n">newKaitaiFileStream</span><span class="p">(</span><span class="n">filename</span><span class="p">),</span><span class="w"> </span><span class="kp">nil</span><span class="p">,</span><span class="w"> </span><span class="kp">nil</span><span class="p">)</span>
 </pre></div>
 
         </div>
@@ -333,7 +442,7 @@ <h3>tcp_segment.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/perl.html b/tcp_segment/perl.html
index 52574f688..39d26d822 100644
--- a/tcp_segment/perl.html
+++ b/tcp_segment/perl.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -305,11 +310,16 @@ <h3>TcpSegment.pm</h3>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">dst_port</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">seq_num</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ack_num</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u4be</span><span class="p">();</span>
-<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">b12</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
-<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">b13</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u1</span><span class="p">();</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">data_offset</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">reserved</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">align_to_byte</span><span class="p">();</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">flags</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nn">TcpSegment::Flags</span><span class="o">-&gt;</span><span class="k">new</span><span class="p">(</span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">},</span><span class="w"> </span><span class="nv">$self</span><span class="p">,</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_root</span><span class="p">});</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">window_size</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">checksum</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">urgent_pointer</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_u2be</span><span class="p">();</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">(((</span><span class="nv">$self</span><span class="o">-&gt;</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span><span class="p">)</span><span class="w"> </span><span class="p">{</span>
+<span class="w">        </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">options</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bytes</span><span class="p">(((</span><span class="nv">$self</span><span class="o">-&gt;</span><span class="n">data_offset</span><span class="p">()</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">));</span>
+<span class="w">    </span><span class="p">}</span>
 <span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">body</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bytes_full</span><span class="p">();</span>
 <span class="p">}</span>
 
@@ -333,14 +343,19 @@ <h3>TcpSegment.pm</h3>
 <span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ack_num</span><span class="p">};</span>
 <span class="p">}</span>
 
-<span class="k">sub</span><span class="w"> </span><span class="nf">b12</span><span class="w"> </span><span class="p">{</span>
+<span class="k">sub</span><span class="w"> </span><span class="nf">data_offset</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">data_offset</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">reserved</span><span class="w"> </span><span class="p">{</span>
 <span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
-<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">b12</span><span class="p">};</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">reserved</span><span class="p">};</span>
 <span class="p">}</span>
 
-<span class="k">sub</span><span class="w"> </span><span class="nf">b13</span><span class="w"> </span><span class="p">{</span>
+<span class="k">sub</span><span class="w"> </span><span class="nf">flags</span><span class="w"> </span><span class="p">{</span>
 <span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
-<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">b13</span><span class="p">};</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">flags</span><span class="p">};</span>
 <span class="p">}</span>
 
 <span class="k">sub</span><span class="w"> </span><span class="nf">window_size</span><span class="w"> </span><span class="p">{</span>
@@ -358,11 +373,96 @@ <h3>TcpSegment.pm</h3>
 <span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">urgent_pointer</span><span class="p">};</span>
 <span class="p">}</span>
 
+<span class="k">sub</span><span class="w"> </span><span class="nf">options</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">options</span><span class="p">};</span>
+<span class="p">}</span>
+
 <span class="k">sub</span><span class="w"> </span><span class="nf">body</span><span class="w"> </span><span class="p">{</span>
 <span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
 <span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">body</span><span class="p">};</span>
 <span class="p">}</span>
 
+<span class="c1">########################################################################</span>
+<span class="k">package</span><span class="w"> </span><span class="nn">TcpSegment::Flags</span><span class="p">;</span>
+
+<span class="k">our</span><span class="w"> </span><span class="nv">@ISA</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">&#39;IO::KaitaiStruct::Struct&#39;</span><span class="p">;</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">from_file</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$class</span><span class="p">,</span><span class="w"> </span><span class="nv">$filename</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="nv">$fd</span><span class="p">;</span>
+
+<span class="w">    </span><span class="nb">open</span><span class="p">(</span><span class="nv">$fd</span><span class="p">,</span><span class="w"> </span><span class="s">&#39;&lt;&#39;</span><span class="p">,</span><span class="w"> </span><span class="nv">$filename</span><span class="p">)</span><span class="w"> </span><span class="ow">or</span><span class="w"> </span><span class="k">return</span><span class="w"> </span><span class="nb">undef</span><span class="p">;</span>
+<span class="w">    </span><span class="nb">binmode</span><span class="p">(</span><span class="nv">$fd</span><span class="p">);</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="k">new</span><span class="p">(</span><span class="nv">$class</span><span class="p">,</span><span class="w"> </span><span class="nn">IO::KaitaiStruct::Stream</span><span class="o">-&gt;</span><span class="k">new</span><span class="p">(</span><span class="nv">$fd</span><span class="p">));</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">new</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$class</span><span class="p">,</span><span class="w"> </span><span class="nv">$_io</span><span class="p">,</span><span class="w"> </span><span class="nv">$_parent</span><span class="p">,</span><span class="w"> </span><span class="nv">$_root</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="nv">$self</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nn">IO::KaitaiStruct::Struct</span><span class="o">-&gt;</span><span class="k">new</span><span class="p">(</span><span class="nv">$_io</span><span class="p">);</span>
+
+<span class="w">    </span><span class="nb">bless</span><span class="w"> </span><span class="nv">$self</span><span class="p">,</span><span class="w"> </span><span class="nv">$class</span><span class="p">;</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_parent</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$_parent</span><span class="p">;</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_root</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$_root</span><span class="w"> </span><span class="o">||</span><span class="w"> </span><span class="nv">$self</span><span class="p">;;</span>
+
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="n">_read</span><span class="p">();</span>
+
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="p">;</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">_read</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">cwr</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ece</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">urg</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ack</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">psh</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">rst</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">syn</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="w">    </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">fin</span><span class="p">}</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">_io</span><span class="p">}</span><span class="o">-&gt;</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">);</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">cwr</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">cwr</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">ece</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ece</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">urg</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">urg</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">ack</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">ack</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">psh</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">psh</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">rst</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">rst</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">syn</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">syn</span><span class="p">};</span>
+<span class="p">}</span>
+
+<span class="k">sub</span><span class="w"> </span><span class="nf">fin</span><span class="w"> </span><span class="p">{</span>
+<span class="w">    </span><span class="k">my</span><span class="w"> </span><span class="p">(</span><span class="nv">$self</span><span class="p">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nv">@_</span><span class="p">;</span>
+<span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="nv">$self</span><span class="o">-&gt;</span><span class="p">{</span><span class="n">fin</span><span class="p">};</span>
+<span class="p">}</span>
+
 <span class="mi">1</span><span class="p">;</span>
 </pre></div>
 
@@ -373,7 +473,7 @@ <h3>TcpSegment.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/php.html b/tcp_segment/php.html
index 5632154aa..ad2506111 100644
--- a/tcp_segment/php.html
+++ b/tcp_segment/php.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -287,35 +292,136 @@ <h3>TcpSegment.php</h3>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_dstPort</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU2be</span><span class="p">();</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_seqNum</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU4be</span><span class="p">();</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ackNum</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU4be</span><span class="p">();</span>
-            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_b12</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU1</span><span class="p">();</span>
-            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_b13</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU1</span><span class="p">();</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_dataOffset</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_reserved</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">4</span><span class="p">);</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">alignToByte</span><span class="p">();</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_flags</span> <span class="o">=</span> <span class="k">new</span> <span class="nx">\TcpSegment\Flags</span><span class="p">(</span><span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="p">,</span> <span class="nv">$this</span><span class="p">,</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_root</span><span class="p">);</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_windowSize</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU2be</span><span class="p">();</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_checksum</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU2be</span><span class="p">();</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_urgentPointer</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readU2be</span><span class="p">();</span>
+            <span class="k">if</span> <span class="p">(((</span><span class="nv">$this</span><span class="o">-&gt;</span><span class="na">dataOffset</span><span class="p">()</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">)</span> <span class="p">{</span>
+                <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_options</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBytes</span><span class="p">(((</span><span class="nv">$this</span><span class="o">-&gt;</span><span class="na">dataOffset</span><span class="p">()</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">));</span>
+            <span class="p">}</span>
             <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_body</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBytesFull</span><span class="p">();</span>
         <span class="p">}</span>
         <span class="k">protected</span> <span class="nv">$_m_srcPort</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_dstPort</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_seqNum</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_ackNum</span><span class="p">;</span>
-        <span class="k">protected</span> <span class="nv">$_m_b12</span><span class="p">;</span>
-        <span class="k">protected</span> <span class="nv">$_m_b13</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_dataOffset</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_reserved</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_flags</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_windowSize</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_checksum</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_urgentPointer</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_options</span><span class="p">;</span>
         <span class="k">protected</span> <span class="nv">$_m_body</span><span class="p">;</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Source port</span>
+<span class="sd">         */</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">srcPort</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_srcPort</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Destination port</span>
+<span class="sd">         */</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">dstPort</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_dstPort</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Sequence number</span>
+<span class="sd">         */</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">seqNum</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_seqNum</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Acknowledgment number</span>
+<span class="sd">         */</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">ackNum</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ackNum</span><span class="p">;</span> <span class="p">}</span>
-        <span class="k">public</span> <span class="k">function</span> <span class="nf">b12</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_b12</span><span class="p">;</span> <span class="p">}</span>
-        <span class="k">public</span> <span class="k">function</span> <span class="nf">b13</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_b13</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">dataOffset</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_dataOffset</span><span class="p">;</span> <span class="p">}</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">reserved</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_reserved</span><span class="p">;</span> <span class="p">}</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">flags</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_flags</span><span class="p">;</span> <span class="p">}</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">windowSize</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_windowSize</span><span class="p">;</span> <span class="p">}</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">checksum</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_checksum</span><span class="p">;</span> <span class="p">}</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">urgentPointer</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_urgentPointer</span><span class="p">;</span> <span class="p">}</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">options</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_options</span><span class="p">;</span> <span class="p">}</span>
         <span class="k">public</span> <span class="k">function</span> <span class="nf">body</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_body</span><span class="p">;</span> <span class="p">}</span>
     <span class="p">}</span>
 <span class="p">}</span>
+
+<span class="sd">/**</span>
+<span class="sd"> * TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="sd"> */</span>
+
+<span class="k">namespace</span> <span class="nx">TcpSegment</span> <span class="p">{</span>
+    <span class="k">class</span> <span class="nc">Flags</span> <span class="k">extends</span> <span class="nx">\Kaitai\Struct\Struct</span> <span class="p">{</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="fm">__construct</span><span class="p">(</span><span class="nx">\Kaitai\Struct\Stream</span> <span class="nv">$_io</span><span class="p">,</span> <span class="nx">\TcpSegment</span> <span class="nv">$_parent</span> <span class="o">=</span> <span class="k">null</span><span class="p">,</span> <span class="nx">\TcpSegment</span> <span class="nv">$_root</span> <span class="o">=</span> <span class="k">null</span><span class="p">)</span> <span class="p">{</span>
+            <span class="k">parent</span><span class="o">::</span><span class="na">__construct</span><span class="p">(</span><span class="nv">$_io</span><span class="p">,</span> <span class="nv">$_parent</span><span class="p">,</span> <span class="nv">$_root</span><span class="p">);</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_read</span><span class="p">();</span>
+        <span class="p">}</span>
+
+        <span class="k">private</span> <span class="k">function</span> <span class="nf">_read</span><span class="p">()</span> <span class="p">{</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_cwr</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ece</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_urg</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ack</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_psh</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_rst</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_syn</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+            <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_fin</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_io</span><span class="o">-&gt;</span><span class="na">readBitsIntBe</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">;</span>
+        <span class="p">}</span>
+        <span class="k">protected</span> <span class="nv">$_m_cwr</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_ece</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_urg</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_ack</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_psh</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_rst</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_syn</span><span class="p">;</span>
+        <span class="k">protected</span> <span class="nv">$_m_fin</span><span class="p">;</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Congestion Window Reduced</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">cwr</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_cwr</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * ECN-Echo</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">ece</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ece</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Urgent pointer field is significant</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">urg</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_urg</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Acknowledgment field is significant</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">ack</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_ack</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Push function</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">psh</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_psh</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Reset the connection</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">rst</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_rst</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * Synchronize sequence numbers</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">syn</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_syn</span><span class="p">;</span> <span class="p">}</span>
+
+        <span class="sd">/**</span>
+<span class="sd">         * No more data from sender</span>
+<span class="sd">         */</span>
+        <span class="k">public</span> <span class="k">function</span> <span class="nf">fin</span><span class="p">()</span> <span class="p">{</span> <span class="k">return</span> <span class="nv">$this</span><span class="o">-&gt;</span><span class="na">_m_fin</span><span class="p">;</span> <span class="p">}</span>
+    <span class="p">}</span>
+<span class="p">}</span>
 </pre></div>
 
         </div>
@@ -325,7 +431,7 @@ <h3>TcpSegment.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/python.html b/tcp_segment/python.html
index c4fa90b60..4ebed9e4e 100644
--- a/tcp_segment/python.html
+++ b/tcp_segment/python.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -281,7 +286,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by invoking getter methods like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="o">.</span><span class="n">src_port</span> <span class="c1"># =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="o">.</span><span class="n">src_port</span> <span class="c1"># =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -335,12 +340,40 @@ <h3>tcp_segment.py</h3>
         <span class="bp">self</span><span class="o">.</span><span class="n">dst_port</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u2be</span><span class="p">()</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">seq_num</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u4be</span><span class="p">()</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">ack_num</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u4be</span><span class="p">()</span>
-        <span class="bp">self</span><span class="o">.</span><span class="n">b12</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u1</span><span class="p">()</span>
-        <span class="bp">self</span><span class="o">.</span><span class="n">b13</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u1</span><span class="p">()</span>
+        <span class="bp">self</span><span class="o">.</span><span class="n">data_offset</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+        <span class="bp">self</span><span class="o">.</span><span class="n">reserved</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+        <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">align_to_byte</span><span class="p">()</span>
+        <span class="bp">self</span><span class="o">.</span><span class="n">flags</span> <span class="o">=</span> <span class="n">TcpSegment</span><span class="o">.</span><span class="n">Flags</span><span class="p">(</span><span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="p">,</span> <span class="bp">self</span><span class="p">,</span> <span class="bp">self</span><span class="o">.</span><span class="n">_root</span><span class="p">)</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">window_size</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u2be</span><span class="p">()</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">checksum</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u2be</span><span class="p">()</span>
         <span class="bp">self</span><span class="o">.</span><span class="n">urgent_pointer</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_u2be</span><span class="p">()</span>
+        <span class="k">if</span> <span class="p">((</span><span class="bp">self</span><span class="o">.</span><span class="n">data_offset</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span><span class="p">:</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">options</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bytes</span><span class="p">(((</span><span class="bp">self</span><span class="o">.</span><span class="n">data_offset</span> <span class="o">*</span> <span class="mi">4</span><span class="p">)</span> <span class="o">-</span> <span class="mi">20</span><span class="p">))</span>
+
         <span class="bp">self</span><span class="o">.</span><span class="n">body</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bytes_full</span><span class="p">()</span>
+
+    <span class="k">class</span> <span class="nc">Flags</span><span class="p">(</span><span class="n">KaitaiStruct</span><span class="p">):</span>
+<span class="w">        </span><span class="sd">&quot;&quot;&quot;TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="sd">        &quot;&quot;&quot;</span>
+        <span class="k">def</span> <span class="fm">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">_io</span><span class="p">,</span> <span class="n">_parent</span><span class="o">=</span><span class="kc">None</span><span class="p">,</span> <span class="n">_root</span><span class="o">=</span><span class="kc">None</span><span class="p">):</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">_io</span> <span class="o">=</span> <span class="n">_io</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">_parent</span> <span class="o">=</span> <span class="n">_parent</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">_root</span> <span class="o">=</span> <span class="n">_root</span> <span class="k">if</span> <span class="n">_root</span> <span class="k">else</span> <span class="bp">self</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">_read</span><span class="p">()</span>
+
+        <span class="k">def</span> <span class="nf">_read</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">cwr</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">ece</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">urg</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">ack</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">psh</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">rst</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">syn</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+            <span class="bp">self</span><span class="o">.</span><span class="n">fin</span> <span class="o">=</span> <span class="bp">self</span><span class="o">.</span><span class="n">_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span> <span class="o">!=</span> <span class="mi">0</span>
+
+
+        <span class="k">def</span> <span class="fm">__repr__</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
+            <span class="k">return</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|CWR&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">cwr</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|ECE&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">ece</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|URG&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">urg</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|ACK&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">ack</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|PSH&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">psh</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|RST&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">rst</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|SYN&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">syn</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span> <span class="o">+</span> <span class="p">(</span><span class="sa">u</span><span class="s2">&quot;|FIN&quot;</span> <span class="k">if</span> <span class="bp">self</span><span class="o">.</span><span class="n">fin</span> <span class="k">else</span> <span class="sa">u</span><span class="s2">&quot;&quot;</span><span class="p">)</span>
 </pre></div>
 
         </div>
@@ -350,7 +383,7 @@ <h3>tcp_segment.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/ruby.html b/tcp_segment/ruby.html
index 35e96e6d9..a52200a88 100644
--- a/tcp_segment/ruby.html
+++ b/tcp_segment/ruby.html
@@ -105,9 +105,9 @@ <h1>TCP (Transmission Control Protocol) segment:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TCP is one of the core Internet protocols on transport layer (AKA
-OSI layer 4), providing stateful connections with error checking,
-guarantees of delivery, order of segments and avoidance of duplicate
+                <p><p>TCP is one of the core Internet protocols on transport layer (AKA<br />
+OSI layer 4), providing stateful connections with error checking,<br />
+guarantees of delivery, order of segments and avoidance of duplicate<br />
 delivery.</p>
 </p>
             </div>
@@ -125,6 +125,10 @@ <h3 class="panel-title">KS implementation details</h3>
                     </div>
                     
                     
+                    <div class="panel-body">
+                        Minimal Kaitai Struct required: 0.1
+                    </div>
+                    
                     
                     
                     
@@ -138,6 +142,7 @@ <h3 class="panel-title">References</h3>
                             
                             <li><a href="https://tools.ietf.org/html/rfc793">RFC 793</a></li>
 <li><a href="https://tools.ietf.org/html/rfc1323">RFC 1323</a></li>
+<li><a href="https://tools.ietf.org/html/rfc9293">RFC 9293</a></li>
                             
                             
                             
@@ -279,7 +284,7 @@ <h3>Code</h3>
 <p>After that, one can get various attributes from the structure by invoking getter methods like:</p>
 
 
-<div class="highlight"><pre><span></span><span class="n">data</span><span class="o">.</span><span class="n">src_port</span><span class="w"> </span><span class="c1"># =&gt; get src port</span>
+<div class="highlight"><pre><span></span><span class="n">data</span><span class="o">.</span><span class="n">src_port</span><span class="w"> </span><span class="c1"># =&gt; Source port</span>
 </pre></div>
 
     </div>
@@ -332,23 +337,102 @@ <h3>tcp_segment.rb</h3>
 <span class="w">    </span><span class="vi">@dst_port</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u2be</span>
 <span class="w">    </span><span class="vi">@seq_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u4be</span>
 <span class="w">    </span><span class="vi">@ack_num</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u4be</span>
-<span class="w">    </span><span class="vi">@b12</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u1</span>
-<span class="w">    </span><span class="vi">@b13</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u1</span>
+<span class="w">    </span><span class="vi">@data_offset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+<span class="w">    </span><span class="vi">@reserved</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">4</span><span class="p">)</span>
+<span class="w">    </span><span class="vi">@_io</span><span class="o">.</span><span class="n">align_to_byte</span>
+<span class="w">    </span><span class="vi">@flags</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="no">Flags</span><span class="o">.</span><span class="n">new</span><span class="p">(</span><span class="vi">@_io</span><span class="p">,</span><span class="w"> </span><span class="nb">self</span><span class="p">,</span><span class="w"> </span><span class="vi">@_root</span><span class="p">)</span>
 <span class="w">    </span><span class="vi">@window_size</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u2be</span>
 <span class="w">    </span><span class="vi">@checksum</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u2be</span>
 <span class="w">    </span><span class="vi">@urgent_pointer</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_u2be</span>
+<span class="w">    </span><span class="k">if</span><span class="w"> </span><span class="p">((</span><span class="n">data_offset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@options</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bytes</span><span class="p">(((</span><span class="n">data_offset</span><span class="w"> </span><span class="o">*</span><span class="w"> </span><span class="mi">4</span><span class="p">)</span><span class="w"> </span><span class="o">-</span><span class="w"> </span><span class="mi">20</span><span class="p">))</span>
+<span class="w">    </span><span class="k">end</span>
 <span class="w">    </span><span class="vi">@body</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bytes_full</span>
 <span class="w">    </span><span class="nb">self</span>
 <span class="w">  </span><span class="k">end</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># TCP header flags as defined &quot;TCP Header Flags&quot; registry.</span>
+<span class="w">  </span><span class="k">class</span><span class="w"> </span><span class="nc">Flags</span><span class="w"> </span><span class="o">&lt;</span><span class="w"> </span><span class="no">Kaitai</span><span class="o">::</span><span class="no">Struct</span><span class="o">::</span><span class="no">Struct</span>
+<span class="w">    </span><span class="k">def</span><span class="w"> </span><span class="nf">initialize</span><span class="p">(</span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="n">_parent</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kp">nil</span><span class="p">,</span><span class="w"> </span><span class="n">_root</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nb">self</span><span class="p">)</span>
+<span class="w">      </span><span class="k">super</span><span class="p">(</span><span class="n">_io</span><span class="p">,</span><span class="w"> </span><span class="n">_parent</span><span class="p">,</span><span class="w"> </span><span class="n">_root</span><span class="p">)</span>
+<span class="w">      </span><span class="n">_read</span>
+<span class="w">    </span><span class="k">end</span>
+
+<span class="w">    </span><span class="k">def</span><span class="w"> </span><span class="n">_read</span>
+<span class="w">      </span><span class="vi">@cwr</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@ece</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@urg</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@ack</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@psh</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@rst</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@syn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="vi">@fin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="vi">@_io</span><span class="o">.</span><span class="n">read_bits_int_be</span><span class="p">(</span><span class="mi">1</span><span class="p">)</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="mi">0</span>
+<span class="w">      </span><span class="nb">self</span>
+<span class="w">    </span><span class="k">end</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Congestion Window Reduced</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:cwr</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># ECN-Echo</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:ece</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Urgent pointer field is significant</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:urg</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Acknowledgment field is significant</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:ack</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Push function</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:psh</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Reset the connection</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:rst</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># Synchronize sequence numbers</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:syn</span>
+
+<span class="w">    </span><span class="c1">##</span>
+<span class="w">    </span><span class="c1"># No more data from sender</span>
+<span class="w">    </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:fin</span>
+
+<span class="w">    </span><span class="k">def</span><span class="w"> </span><span class="nf">inspect</span>
+<span class="w">      </span><span class="p">(</span><span class="n">cwr</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|CWR&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">ece</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|ECE&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">urg</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|URG&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">ack</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|ACK&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">psh</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|PSH&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">rst</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|RST&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">syn</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|SYN&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="p">(</span><span class="n">fin</span><span class="w"> </span><span class="p">?</span><span class="w"> </span><span class="s2">&quot;|FIN&quot;</span><span class="w"> </span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;&quot;</span><span class="p">)</span>
+<span class="w">    </span><span class="k">end</span>
+<span class="w">  </span><span class="k">end</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># Source port</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:src_port</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># Destination port</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:dst_port</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># Sequence number</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:seq_num</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># Acknowledgment number</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:ack_num</span>
-<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:b12</span>
-<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:b13</span>
+
+<span class="w">  </span><span class="c1">##</span>
+<span class="w">  </span><span class="c1"># Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)</span>
+<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:data_offset</span>
+<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:reserved</span>
+<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:flags</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:window_size</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:checksum</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:urgent_pointer</span>
+<span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:options</span>
 <span class="w">  </span><span class="kp">attr_reader</span><span class="w"> </span><span class="ss">:body</span>
 <span class="k">end</span>
 </pre></div>
@@ -360,7 +444,7 @@ <h3>tcp_segment.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tcp_segment/src/cpp_stl_11/tcp_segment.cpp b/tcp_segment/src/cpp_stl_11/tcp_segment.cpp
index ce242b767..b1585c8ac 100644
--- a/tcp_segment/src/cpp_stl_11/tcp_segment.cpp
+++ b/tcp_segment/src/cpp_stl_11/tcp_segment.cpp
@@ -5,6 +5,7 @@
 tcp_segment_t::tcp_segment_t(kaitai::kstream* p__io, kaitai::kstruct* p__parent, tcp_segment_t* p__root) : kaitai::kstruct(p__io) {
     m__parent = p__parent;
     m__root = this;
+    m_flags = nullptr;
     _read();
 }
 
@@ -13,11 +14,18 @@ void tcp_segment_t::_read() {
     m_dst_port = m__io->read_u2be();
     m_seq_num = m__io->read_u4be();
     m_ack_num = m__io->read_u4be();
-    m_b12 = m__io->read_u1();
-    m_b13 = m__io->read_u1();
+    m_data_offset = m__io->read_bits_int_be(4);
+    m_reserved = m__io->read_bits_int_be(4);
+    m__io->align_to_byte();
+    m_flags = std::unique_ptr<flags_t>(new flags_t(m__io, this, m__root));
     m_window_size = m__io->read_u2be();
     m_checksum = m__io->read_u2be();
     m_urgent_pointer = m__io->read_u2be();
+    n_options = true;
+    if (((data_offset() * 4) - 20) != 0) {
+        n_options = false;
+        m_options = m__io->read_bytes(((data_offset() * 4) - 20));
+    }
     m_body = m__io->read_bytes_full();
 }
 
@@ -26,4 +34,30 @@ tcp_segment_t::~tcp_segment_t() {
 }
 
 void tcp_segment_t::_clean_up() {
+    if (!n_options) {
+    }
+}
+
+tcp_segment_t::flags_t::flags_t(kaitai::kstream* p__io, tcp_segment_t* p__parent, tcp_segment_t* p__root) : kaitai::kstruct(p__io) {
+    m__parent = p__parent;
+    m__root = p__root;
+    _read();
+}
+
+void tcp_segment_t::flags_t::_read() {
+    m_cwr = m__io->read_bits_int_be(1);
+    m_ece = m__io->read_bits_int_be(1);
+    m_urg = m__io->read_bits_int_be(1);
+    m_ack = m__io->read_bits_int_be(1);
+    m_psh = m__io->read_bits_int_be(1);
+    m_rst = m__io->read_bits_int_be(1);
+    m_syn = m__io->read_bits_int_be(1);
+    m_fin = m__io->read_bits_int_be(1);
+}
+
+tcp_segment_t::flags_t::~flags_t() {
+    _clean_up();
+}
+
+void tcp_segment_t::flags_t::_clean_up() {
 }
diff --git a/tcp_segment/src/cpp_stl_11/tcp_segment.h b/tcp_segment/src/cpp_stl_11/tcp_segment.h
index af208a1ba..dcf2dfc62 100644
--- a/tcp_segment/src/cpp_stl_11/tcp_segment.h
+++ b/tcp_segment/src/cpp_stl_11/tcp_segment.h
@@ -20,6 +20,7 @@
 class tcp_segment_t : public kaitai::kstruct {
 
 public:
+    class flags_t;
 
     tcp_segment_t(kaitai::kstream* p__io, kaitai::kstruct* p__parent = nullptr, tcp_segment_t* p__root = nullptr);
 
@@ -30,30 +31,134 @@ class tcp_segment_t : public kaitai::kstruct {
 public:
     ~tcp_segment_t();
 
+    /**
+     * TCP header flags as defined "TCP Header Flags" registry.
+     */
+
+    class flags_t : public kaitai::kstruct {
+
+    public:
+
+        flags_t(kaitai::kstream* p__io, tcp_segment_t* p__parent = nullptr, tcp_segment_t* p__root = nullptr);
+
+    private:
+        void _read();
+        void _clean_up();
+
+    public:
+        ~flags_t();
+
+    private:
+        bool m_cwr;
+        bool m_ece;
+        bool m_urg;
+        bool m_ack;
+        bool m_psh;
+        bool m_rst;
+        bool m_syn;
+        bool m_fin;
+        tcp_segment_t* m__root;
+        tcp_segment_t* m__parent;
+
+    public:
+
+        /**
+         * Congestion Window Reduced
+         */
+        bool cwr() const { return m_cwr; }
+
+        /**
+         * ECN-Echo
+         */
+        bool ece() const { return m_ece; }
+
+        /**
+         * Urgent pointer field is significant
+         */
+        bool urg() const { return m_urg; }
+
+        /**
+         * Acknowledgment field is significant
+         */
+        bool ack() const { return m_ack; }
+
+        /**
+         * Push function
+         */
+        bool psh() const { return m_psh; }
+
+        /**
+         * Reset the connection
+         */
+        bool rst() const { return m_rst; }
+
+        /**
+         * Synchronize sequence numbers
+         */
+        bool syn() const { return m_syn; }
+
+        /**
+         * No more data from sender
+         */
+        bool fin() const { return m_fin; }
+        tcp_segment_t* _root() const { return m__root; }
+        tcp_segment_t* _parent() const { return m__parent; }
+    };
+
 private:
     uint16_t m_src_port;
     uint16_t m_dst_port;
     uint32_t m_seq_num;
     uint32_t m_ack_num;
-    uint8_t m_b12;
-    uint8_t m_b13;
+    uint64_t m_data_offset;
+    uint64_t m_reserved;
+    std::unique_ptr<flags_t> m_flags;
     uint16_t m_window_size;
     uint16_t m_checksum;
     uint16_t m_urgent_pointer;
+    std::string m_options;
+    bool n_options;
+
+public:
+    bool _is_null_options() { options(); return n_options; };
+
+private:
     std::string m_body;
     tcp_segment_t* m__root;
     kaitai::kstruct* m__parent;
 
 public:
+
+    /**
+     * Source port
+     */
     uint16_t src_port() const { return m_src_port; }
+
+    /**
+     * Destination port
+     */
     uint16_t dst_port() const { return m_dst_port; }
+
+    /**
+     * Sequence number
+     */
     uint32_t seq_num() const { return m_seq_num; }
+
+    /**
+     * Acknowledgment number
+     */
     uint32_t ack_num() const { return m_ack_num; }
-    uint8_t b12() const { return m_b12; }
-    uint8_t b13() const { return m_b13; }
+
+    /**
+     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+     */
+    uint64_t data_offset() const { return m_data_offset; }
+    uint64_t reserved() const { return m_reserved; }
+    flags_t* flags() const { return m_flags.get(); }
     uint16_t window_size() const { return m_window_size; }
     uint16_t checksum() const { return m_checksum; }
     uint16_t urgent_pointer() const { return m_urgent_pointer; }
+    std::string options() const { return m_options; }
     std::string body() const { return m_body; }
     tcp_segment_t* _root() const { return m__root; }
     kaitai::kstruct* _parent() const { return m__parent; }
diff --git a/tcp_segment/src/cpp_stl_98/tcp_segment.cpp b/tcp_segment/src/cpp_stl_98/tcp_segment.cpp
index e31781481..843765a77 100644
--- a/tcp_segment/src/cpp_stl_98/tcp_segment.cpp
+++ b/tcp_segment/src/cpp_stl_98/tcp_segment.cpp
@@ -5,6 +5,7 @@
 tcp_segment_t::tcp_segment_t(kaitai::kstream* p__io, kaitai::kstruct* p__parent, tcp_segment_t* p__root) : kaitai::kstruct(p__io) {
     m__parent = p__parent;
     m__root = this;
+    m_flags = 0;
 
     try {
         _read();
@@ -19,11 +20,18 @@ void tcp_segment_t::_read() {
     m_dst_port = m__io->read_u2be();
     m_seq_num = m__io->read_u4be();
     m_ack_num = m__io->read_u4be();
-    m_b12 = m__io->read_u1();
-    m_b13 = m__io->read_u1();
+    m_data_offset = m__io->read_bits_int_be(4);
+    m_reserved = m__io->read_bits_int_be(4);
+    m__io->align_to_byte();
+    m_flags = new flags_t(m__io, this, m__root);
     m_window_size = m__io->read_u2be();
     m_checksum = m__io->read_u2be();
     m_urgent_pointer = m__io->read_u2be();
+    n_options = true;
+    if (((data_offset() * 4) - 20) != 0) {
+        n_options = false;
+        m_options = m__io->read_bytes(((data_offset() * 4) - 20));
+    }
     m_body = m__io->read_bytes_full();
 }
 
@@ -32,4 +40,39 @@ tcp_segment_t::~tcp_segment_t() {
 }
 
 void tcp_segment_t::_clean_up() {
+    if (m_flags) {
+        delete m_flags; m_flags = 0;
+    }
+    if (!n_options) {
+    }
+}
+
+tcp_segment_t::flags_t::flags_t(kaitai::kstream* p__io, tcp_segment_t* p__parent, tcp_segment_t* p__root) : kaitai::kstruct(p__io) {
+    m__parent = p__parent;
+    m__root = p__root;
+
+    try {
+        _read();
+    } catch(...) {
+        _clean_up();
+        throw;
+    }
+}
+
+void tcp_segment_t::flags_t::_read() {
+    m_cwr = m__io->read_bits_int_be(1);
+    m_ece = m__io->read_bits_int_be(1);
+    m_urg = m__io->read_bits_int_be(1);
+    m_ack = m__io->read_bits_int_be(1);
+    m_psh = m__io->read_bits_int_be(1);
+    m_rst = m__io->read_bits_int_be(1);
+    m_syn = m__io->read_bits_int_be(1);
+    m_fin = m__io->read_bits_int_be(1);
+}
+
+tcp_segment_t::flags_t::~flags_t() {
+    _clean_up();
+}
+
+void tcp_segment_t::flags_t::_clean_up() {
 }
diff --git a/tcp_segment/src/cpp_stl_98/tcp_segment.h b/tcp_segment/src/cpp_stl_98/tcp_segment.h
index a91c155b1..cd83b045c 100644
--- a/tcp_segment/src/cpp_stl_98/tcp_segment.h
+++ b/tcp_segment/src/cpp_stl_98/tcp_segment.h
@@ -20,6 +20,7 @@
 class tcp_segment_t : public kaitai::kstruct {
 
 public:
+    class flags_t;
 
     tcp_segment_t(kaitai::kstream* p__io, kaitai::kstruct* p__parent = 0, tcp_segment_t* p__root = 0);
 
@@ -30,30 +31,134 @@ class tcp_segment_t : public kaitai::kstruct {
 public:
     ~tcp_segment_t();
 
+    /**
+     * TCP header flags as defined "TCP Header Flags" registry.
+     */
+
+    class flags_t : public kaitai::kstruct {
+
+    public:
+
+        flags_t(kaitai::kstream* p__io, tcp_segment_t* p__parent = 0, tcp_segment_t* p__root = 0);
+
+    private:
+        void _read();
+        void _clean_up();
+
+    public:
+        ~flags_t();
+
+    private:
+        bool m_cwr;
+        bool m_ece;
+        bool m_urg;
+        bool m_ack;
+        bool m_psh;
+        bool m_rst;
+        bool m_syn;
+        bool m_fin;
+        tcp_segment_t* m__root;
+        tcp_segment_t* m__parent;
+
+    public:
+
+        /**
+         * Congestion Window Reduced
+         */
+        bool cwr() const { return m_cwr; }
+
+        /**
+         * ECN-Echo
+         */
+        bool ece() const { return m_ece; }
+
+        /**
+         * Urgent pointer field is significant
+         */
+        bool urg() const { return m_urg; }
+
+        /**
+         * Acknowledgment field is significant
+         */
+        bool ack() const { return m_ack; }
+
+        /**
+         * Push function
+         */
+        bool psh() const { return m_psh; }
+
+        /**
+         * Reset the connection
+         */
+        bool rst() const { return m_rst; }
+
+        /**
+         * Synchronize sequence numbers
+         */
+        bool syn() const { return m_syn; }
+
+        /**
+         * No more data from sender
+         */
+        bool fin() const { return m_fin; }
+        tcp_segment_t* _root() const { return m__root; }
+        tcp_segment_t* _parent() const { return m__parent; }
+    };
+
 private:
     uint16_t m_src_port;
     uint16_t m_dst_port;
     uint32_t m_seq_num;
     uint32_t m_ack_num;
-    uint8_t m_b12;
-    uint8_t m_b13;
+    uint64_t m_data_offset;
+    uint64_t m_reserved;
+    flags_t* m_flags;
     uint16_t m_window_size;
     uint16_t m_checksum;
     uint16_t m_urgent_pointer;
+    std::string m_options;
+    bool n_options;
+
+public:
+    bool _is_null_options() { options(); return n_options; };
+
+private:
     std::string m_body;
     tcp_segment_t* m__root;
     kaitai::kstruct* m__parent;
 
 public:
+
+    /**
+     * Source port
+     */
     uint16_t src_port() const { return m_src_port; }
+
+    /**
+     * Destination port
+     */
     uint16_t dst_port() const { return m_dst_port; }
+
+    /**
+     * Sequence number
+     */
     uint32_t seq_num() const { return m_seq_num; }
+
+    /**
+     * Acknowledgment number
+     */
     uint32_t ack_num() const { return m_ack_num; }
-    uint8_t b12() const { return m_b12; }
-    uint8_t b13() const { return m_b13; }
+
+    /**
+     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+     */
+    uint64_t data_offset() const { return m_data_offset; }
+    uint64_t reserved() const { return m_reserved; }
+    flags_t* flags() const { return m_flags; }
     uint16_t window_size() const { return m_window_size; }
     uint16_t checksum() const { return m_checksum; }
     uint16_t urgent_pointer() const { return m_urgent_pointer; }
+    std::string options() const { return m_options; }
     std::string body() const { return m_body; }
     tcp_segment_t* _root() const { return m__root; }
     kaitai::kstruct* _parent() const { return m__parent; }
diff --git a/tcp_segment/src/csharp/TcpSegment.cs b/tcp_segment/src/csharp/TcpSegment.cs
index c8d833427..6ae8f6821 100644
--- a/tcp_segment/src/csharp/TcpSegment.cs
+++ b/tcp_segment/src/csharp/TcpSegment.cs
@@ -30,34 +30,144 @@ private void _read()
             _dstPort = m_io.ReadU2be();
             _seqNum = m_io.ReadU4be();
             _ackNum = m_io.ReadU4be();
-            _b12 = m_io.ReadU1();
-            _b13 = m_io.ReadU1();
+            _dataOffset = m_io.ReadBitsIntBe(4);
+            _reserved = m_io.ReadBitsIntBe(4);
+            m_io.AlignToByte();
+            _flags = new Flags(m_io, this, m_root);
             _windowSize = m_io.ReadU2be();
             _checksum = m_io.ReadU2be();
             _urgentPointer = m_io.ReadU2be();
+            if (((DataOffset * 4) - 20) != 0) {
+                _options = m_io.ReadBytes(((DataOffset * 4) - 20));
+            }
             _body = m_io.ReadBytesFull();
         }
+
+        /// <summary>
+        /// TCP header flags as defined &quot;TCP Header Flags&quot; registry.
+        /// </summary>
+        public partial class Flags : KaitaiStruct
+        {
+            public static Flags FromFile(string fileName)
+            {
+                return new Flags(new KaitaiStream(fileName));
+            }
+
+            public Flags(KaitaiStream p__io, TcpSegment p__parent = null, TcpSegment p__root = null) : base(p__io)
+            {
+                m_parent = p__parent;
+                m_root = p__root;
+                _read();
+            }
+            private void _read()
+            {
+                _cwr = m_io.ReadBitsIntBe(1) != 0;
+                _ece = m_io.ReadBitsIntBe(1) != 0;
+                _urg = m_io.ReadBitsIntBe(1) != 0;
+                _ack = m_io.ReadBitsIntBe(1) != 0;
+                _psh = m_io.ReadBitsIntBe(1) != 0;
+                _rst = m_io.ReadBitsIntBe(1) != 0;
+                _syn = m_io.ReadBitsIntBe(1) != 0;
+                _fin = m_io.ReadBitsIntBe(1) != 0;
+            }
+            private bool _cwr;
+            private bool _ece;
+            private bool _urg;
+            private bool _ack;
+            private bool _psh;
+            private bool _rst;
+            private bool _syn;
+            private bool _fin;
+            private TcpSegment m_root;
+            private TcpSegment m_parent;
+
+            /// <summary>
+            /// Congestion Window Reduced
+            /// </summary>
+            public bool Cwr { get { return _cwr; } }
+
+            /// <summary>
+            /// ECN-Echo
+            /// </summary>
+            public bool Ece { get { return _ece; } }
+
+            /// <summary>
+            /// Urgent pointer field is significant
+            /// </summary>
+            public bool Urg { get { return _urg; } }
+
+            /// <summary>
+            /// Acknowledgment field is significant
+            /// </summary>
+            public bool Ack { get { return _ack; } }
+
+            /// <summary>
+            /// Push function
+            /// </summary>
+            public bool Psh { get { return _psh; } }
+
+            /// <summary>
+            /// Reset the connection
+            /// </summary>
+            public bool Rst { get { return _rst; } }
+
+            /// <summary>
+            /// Synchronize sequence numbers
+            /// </summary>
+            public bool Syn { get { return _syn; } }
+
+            /// <summary>
+            /// No more data from sender
+            /// </summary>
+            public bool Fin { get { return _fin; } }
+            public TcpSegment M_Root { get { return m_root; } }
+            public TcpSegment M_Parent { get { return m_parent; } }
+        }
         private ushort _srcPort;
         private ushort _dstPort;
         private uint _seqNum;
         private uint _ackNum;
-        private byte _b12;
-        private byte _b13;
+        private ulong _dataOffset;
+        private ulong _reserved;
+        private Flags _flags;
         private ushort _windowSize;
         private ushort _checksum;
         private ushort _urgentPointer;
+        private byte[] _options;
         private byte[] _body;
         private TcpSegment m_root;
         private KaitaiStruct m_parent;
+
+        /// <summary>
+        /// Source port
+        /// </summary>
         public ushort SrcPort { get { return _srcPort; } }
+
+        /// <summary>
+        /// Destination port
+        /// </summary>
         public ushort DstPort { get { return _dstPort; } }
+
+        /// <summary>
+        /// Sequence number
+        /// </summary>
         public uint SeqNum { get { return _seqNum; } }
+
+        /// <summary>
+        /// Acknowledgment number
+        /// </summary>
         public uint AckNum { get { return _ackNum; } }
-        public byte B12 { get { return _b12; } }
-        public byte B13 { get { return _b13; } }
+
+        /// <summary>
+        /// Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+        /// </summary>
+        public ulong DataOffset { get { return _dataOffset; } }
+        public ulong Reserved { get { return _reserved; } }
+        public Flags Flags { get { return _flags; } }
         public ushort WindowSize { get { return _windowSize; } }
         public ushort Checksum { get { return _checksum; } }
         public ushort UrgentPointer { get { return _urgentPointer; } }
+        public byte[] Options { get { return _options; } }
         public byte[] Body { get { return _body; } }
         public TcpSegment M_Root { get { return m_root; } }
         public KaitaiStruct M_Parent { get { return m_parent; } }
diff --git a/tcp_segment/src/go/tcp_segment.go b/tcp_segment/src/go/tcp_segment.go
index ecb8849ca..679077b3f 100644
--- a/tcp_segment/src/go/tcp_segment.go
+++ b/tcp_segment/src/go/tcp_segment.go
@@ -14,11 +14,13 @@ type TcpSegment struct {
 	DstPort uint16
 	SeqNum uint32
 	AckNum uint32
-	B12 uint8
-	B13 uint8
+	DataOffset uint64
+	Reserved uint64
+	Flags *TcpSegment_Flags
 	WindowSize uint16
 	Checksum uint16
 	UrgentPointer uint16
+	Options []byte
 	Body []byte
 	_io *kaitai.Stream
 	_root *TcpSegment
@@ -54,36 +56,172 @@ func (this *TcpSegment) Read(io *kaitai.Stream, parent interface{}, root *TcpSeg
 		return err
 	}
 	this.AckNum = uint32(tmp4)
-	tmp5, err := this._io.ReadU1()
+	tmp5, err := this._io.ReadBitsIntBe(4)
 	if err != nil {
 		return err
 	}
-	this.B12 = tmp5
-	tmp6, err := this._io.ReadU1()
+	this.DataOffset = tmp5
+	tmp6, err := this._io.ReadBitsIntBe(4)
 	if err != nil {
 		return err
 	}
-	this.B13 = tmp6
-	tmp7, err := this._io.ReadU2be()
+	this.Reserved = tmp6
+	this._io.AlignToByte()
+	tmp7 := NewTcpSegment_Flags()
+	err = tmp7.Read(this._io, this, this._root)
 	if err != nil {
 		return err
 	}
-	this.WindowSize = uint16(tmp7)
+	this.Flags = tmp7
 	tmp8, err := this._io.ReadU2be()
 	if err != nil {
 		return err
 	}
-	this.Checksum = uint16(tmp8)
+	this.WindowSize = uint16(tmp8)
 	tmp9, err := this._io.ReadU2be()
 	if err != nil {
 		return err
 	}
-	this.UrgentPointer = uint16(tmp9)
-	tmp10, err := this._io.ReadBytesFull()
+	this.Checksum = uint16(tmp9)
+	tmp10, err := this._io.ReadU2be()
 	if err != nil {
 		return err
 	}
-	tmp10 = tmp10
-	this.Body = tmp10
+	this.UrgentPointer = uint16(tmp10)
+	if (((this.DataOffset * 4) - 20) != 0) {
+		tmp11, err := this._io.ReadBytes(int(((this.DataOffset * 4) - 20)))
+		if err != nil {
+			return err
+		}
+		tmp11 = tmp11
+		this.Options = tmp11
+	}
+	tmp12, err := this._io.ReadBytesFull()
+	if err != nil {
+		return err
+	}
+	tmp12 = tmp12
+	this.Body = tmp12
+	return err
+}
+
+/**
+ * Source port
+ */
+
+/**
+ * Destination port
+ */
+
+/**
+ * Sequence number
+ */
+
+/**
+ * Acknowledgment number
+ */
+
+/**
+ * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+ */
+
+/**
+ * TCP header flags as defined "TCP Header Flags" registry.
+ */
+type TcpSegment_Flags struct {
+	Cwr bool
+	Ece bool
+	Urg bool
+	Ack bool
+	Psh bool
+	Rst bool
+	Syn bool
+	Fin bool
+	_io *kaitai.Stream
+	_root *TcpSegment
+	_parent *TcpSegment
+}
+func NewTcpSegment_Flags() *TcpSegment_Flags {
+	return &TcpSegment_Flags{
+	}
+}
+
+func (this *TcpSegment_Flags) Read(io *kaitai.Stream, parent *TcpSegment, root *TcpSegment) (err error) {
+	this._io = io
+	this._parent = parent
+	this._root = root
+
+	tmp13, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Cwr = tmp13 != 0
+	tmp14, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Ece = tmp14 != 0
+	tmp15, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Urg = tmp15 != 0
+	tmp16, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Ack = tmp16 != 0
+	tmp17, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Psh = tmp17 != 0
+	tmp18, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Rst = tmp18 != 0
+	tmp19, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Syn = tmp19 != 0
+	tmp20, err := this._io.ReadBitsIntBe(1)
+	if err != nil {
+		return err
+	}
+	this.Fin = tmp20 != 0
 	return err
 }
+
+/**
+ * Congestion Window Reduced
+ */
+
+/**
+ * ECN-Echo
+ */
+
+/**
+ * Urgent pointer field is significant
+ */
+
+/**
+ * Acknowledgment field is significant
+ */
+
+/**
+ * Push function
+ */
+
+/**
+ * Reset the connection
+ */
+
+/**
+ * Synchronize sequence numbers
+ */
+
+/**
+ * No more data from sender
+ */
diff --git a/tcp_segment/src/graphviz/tcp_segment.dot b/tcp_segment/src/graphviz/tcp_segment.dot
index f3a53ae70..8313ab336 100644
--- a/tcp_segment/src/graphviz/tcp_segment.dot
+++ b/tcp_segment/src/graphviz/tcp_segment.dot
@@ -11,12 +11,32 @@ digraph {
 			<TR><TD PORT="dst_port_pos">2</TD><TD PORT="dst_port_size">2</TD><TD>u2be</TD><TD PORT="dst_port_type">dst_port</TD></TR>
 			<TR><TD PORT="seq_num_pos">4</TD><TD PORT="seq_num_size">4</TD><TD>u4be</TD><TD PORT="seq_num_type">seq_num</TD></TR>
 			<TR><TD PORT="ack_num_pos">8</TD><TD PORT="ack_num_size">4</TD><TD>u4be</TD><TD PORT="ack_num_type">ack_num</TD></TR>
-			<TR><TD PORT="b12_pos">12</TD><TD PORT="b12_size">1</TD><TD>u1</TD><TD PORT="b12_type">b12</TD></TR>
-			<TR><TD PORT="b13_pos">13</TD><TD PORT="b13_size">1</TD><TD>u1</TD><TD PORT="b13_type">b13</TD></TR>
+			<TR><TD PORT="data_offset_pos">12</TD><TD PORT="data_offset_size">4b</TD><TD>b4</TD><TD PORT="data_offset_type">data_offset</TD></TR>
+			<TR><TD PORT="reserved_pos">12:4</TD><TD PORT="reserved_size">4b</TD><TD>b4</TD><TD PORT="reserved_type">reserved</TD></TR>
+			<TR><TD PORT="flags_pos">13</TD><TD PORT="flags_size">1</TD><TD>Flags</TD><TD PORT="flags_type">flags</TD></TR>
 			<TR><TD PORT="window_size_pos">14</TD><TD PORT="window_size_size">2</TD><TD>u2be</TD><TD PORT="window_size_type">window_size</TD></TR>
 			<TR><TD PORT="checksum_pos">16</TD><TD PORT="checksum_size">2</TD><TD>u2be</TD><TD PORT="checksum_type">checksum</TD></TR>
 			<TR><TD PORT="urgent_pointer_pos">18</TD><TD PORT="urgent_pointer_size">2</TD><TD>u2be</TD><TD PORT="urgent_pointer_type">urgent_pointer</TD></TR>
-			<TR><TD PORT="body_pos">20</TD><TD PORT="body_size">⇲</TD><TD></TD><TD PORT="body_type">body</TD></TR>
+			<TR><TD PORT="options_pos">20</TD><TD PORT="options_size">((data_offset * 4) - 20)</TD><TD></TD><TD PORT="options_type">options</TD></TR>
+			<TR><TD PORT="body_pos">...</TD><TD PORT="body_size">⇲</TD><TD></TD><TD PORT="body_type">body</TD></TR>
 		</TABLE>>];
+		subgraph cluster__flags {
+			label="TcpSegment::Flags";
+			graph[style=dotted];
+
+			flags__seq [label=<<TABLE BORDER="0" CELLBORDER="1" CELLSPACING="0">
+				<TR><TD BGCOLOR="#E0FFE0">pos</TD><TD BGCOLOR="#E0FFE0">size</TD><TD BGCOLOR="#E0FFE0">type</TD><TD BGCOLOR="#E0FFE0">id</TD></TR>
+				<TR><TD PORT="cwr_pos">0</TD><TD PORT="cwr_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="cwr_type">cwr</TD></TR>
+				<TR><TD PORT="ece_pos">0:1</TD><TD PORT="ece_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="ece_type">ece</TD></TR>
+				<TR><TD PORT="urg_pos">0:2</TD><TD PORT="urg_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="urg_type">urg</TD></TR>
+				<TR><TD PORT="ack_pos">0:3</TD><TD PORT="ack_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="ack_type">ack</TD></TR>
+				<TR><TD PORT="psh_pos">0:4</TD><TD PORT="psh_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="psh_type">psh</TD></TR>
+				<TR><TD PORT="rst_pos">0:5</TD><TD PORT="rst_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="rst_type">rst</TD></TR>
+				<TR><TD PORT="syn_pos">0:6</TD><TD PORT="syn_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="syn_type">syn</TD></TR>
+				<TR><TD PORT="fin_pos">0:7</TD><TD PORT="fin_size">1b</TD><TD>BitsType1(BigBitEndian)</TD><TD PORT="fin_type">fin</TD></TR>
+			</TABLE>>];
+		}
 	}
+	tcp_segment__seq:flags_type -> flags__seq [style=bold];
+	tcp_segment__seq:data_offset_type -> tcp_segment__seq:options_size [color="#404040"];
 }
diff --git a/tcp_segment/src/java/TcpSegment.java b/tcp_segment/src/java/TcpSegment.java
index d2422567d..d06c66779 100644
--- a/tcp_segment/src/java/TcpSegment.java
+++ b/tcp_segment/src/java/TcpSegment.java
@@ -36,34 +36,149 @@ private void _read() {
         this.dstPort = this._io.readU2be();
         this.seqNum = this._io.readU4be();
         this.ackNum = this._io.readU4be();
-        this.b12 = this._io.readU1();
-        this.b13 = this._io.readU1();
+        this.dataOffset = this._io.readBitsIntBe(4);
+        this.reserved = this._io.readBitsIntBe(4);
+        this._io.alignToByte();
+        this.flags = new Flags(this._io, this, _root);
         this.windowSize = this._io.readU2be();
         this.checksum = this._io.readU2be();
         this.urgentPointer = this._io.readU2be();
+        if (((dataOffset() * 4) - 20) != 0) {
+            this.options = this._io.readBytes(((dataOffset() * 4) - 20));
+        }
         this.body = this._io.readBytesFull();
     }
+
+    /**
+     * TCP header flags as defined "TCP Header Flags" registry.
+     */
+    public static class Flags extends KaitaiStruct {
+        public static Flags fromFile(String fileName) throws IOException {
+            return new Flags(new ByteBufferKaitaiStream(fileName));
+        }
+
+        public Flags(KaitaiStream _io) {
+            this(_io, null, null);
+        }
+
+        public Flags(KaitaiStream _io, TcpSegment _parent) {
+            this(_io, _parent, null);
+        }
+
+        public Flags(KaitaiStream _io, TcpSegment _parent, TcpSegment _root) {
+            super(_io);
+            this._parent = _parent;
+            this._root = _root;
+            _read();
+        }
+        private void _read() {
+            this.cwr = this._io.readBitsIntBe(1) != 0;
+            this.ece = this._io.readBitsIntBe(1) != 0;
+            this.urg = this._io.readBitsIntBe(1) != 0;
+            this.ack = this._io.readBitsIntBe(1) != 0;
+            this.psh = this._io.readBitsIntBe(1) != 0;
+            this.rst = this._io.readBitsIntBe(1) != 0;
+            this.syn = this._io.readBitsIntBe(1) != 0;
+            this.fin = this._io.readBitsIntBe(1) != 0;
+        }
+        private boolean cwr;
+        private boolean ece;
+        private boolean urg;
+        private boolean ack;
+        private boolean psh;
+        private boolean rst;
+        private boolean syn;
+        private boolean fin;
+        private TcpSegment _root;
+        private TcpSegment _parent;
+
+        /**
+         * Congestion Window Reduced
+         */
+        public boolean cwr() { return cwr; }
+
+        /**
+         * ECN-Echo
+         */
+        public boolean ece() { return ece; }
+
+        /**
+         * Urgent pointer field is significant
+         */
+        public boolean urg() { return urg; }
+
+        /**
+         * Acknowledgment field is significant
+         */
+        public boolean ack() { return ack; }
+
+        /**
+         * Push function
+         */
+        public boolean psh() { return psh; }
+
+        /**
+         * Reset the connection
+         */
+        public boolean rst() { return rst; }
+
+        /**
+         * Synchronize sequence numbers
+         */
+        public boolean syn() { return syn; }
+
+        /**
+         * No more data from sender
+         */
+        public boolean fin() { return fin; }
+        public TcpSegment _root() { return _root; }
+        public TcpSegment _parent() { return _parent; }
+    }
     private int srcPort;
     private int dstPort;
     private long seqNum;
     private long ackNum;
-    private int b12;
-    private int b13;
+    private long dataOffset;
+    private long reserved;
+    private Flags flags;
     private int windowSize;
     private int checksum;
     private int urgentPointer;
+    private byte[] options;
     private byte[] body;
     private TcpSegment _root;
     private KaitaiStruct _parent;
+
+    /**
+     * Source port
+     */
     public int srcPort() { return srcPort; }
+
+    /**
+     * Destination port
+     */
     public int dstPort() { return dstPort; }
+
+    /**
+     * Sequence number
+     */
     public long seqNum() { return seqNum; }
+
+    /**
+     * Acknowledgment number
+     */
     public long ackNum() { return ackNum; }
-    public int b12() { return b12; }
-    public int b13() { return b13; }
+
+    /**
+     * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+     */
+    public long dataOffset() { return dataOffset; }
+    public long reserved() { return reserved; }
+    public Flags flags() { return flags; }
     public int windowSize() { return windowSize; }
     public int checksum() { return checksum; }
     public int urgentPointer() { return urgentPointer; }
+    public byte[] options() { return options; }
     public byte[] body() { return body; }
     public TcpSegment _root() { return _root; }
     public KaitaiStruct _parent() { return _parent; }
diff --git a/tcp_segment/src/javascript/TcpSegment.js b/tcp_segment/src/javascript/TcpSegment.js
index fc726f377..9e41b2af5 100644
--- a/tcp_segment/src/javascript/TcpSegment.js
+++ b/tcp_segment/src/javascript/TcpSegment.js
@@ -29,14 +29,101 @@ var TcpSegment = (function() {
     this.dstPort = this._io.readU2be();
     this.seqNum = this._io.readU4be();
     this.ackNum = this._io.readU4be();
-    this.b12 = this._io.readU1();
-    this.b13 = this._io.readU1();
+    this.dataOffset = this._io.readBitsIntBe(4);
+    this.reserved = this._io.readBitsIntBe(4);
+    this._io.alignToByte();
+    this.flags = new Flags(this._io, this, this._root);
     this.windowSize = this._io.readU2be();
     this.checksum = this._io.readU2be();
     this.urgentPointer = this._io.readU2be();
+    if (((this.dataOffset * 4) - 20) != 0) {
+      this.options = this._io.readBytes(((this.dataOffset * 4) - 20));
+    }
     this.body = this._io.readBytesFull();
   }
 
+  /**
+   * TCP header flags as defined "TCP Header Flags" registry.
+   */
+
+  var Flags = TcpSegment.Flags = (function() {
+    function Flags(_io, _parent, _root) {
+      this._io = _io;
+      this._parent = _parent;
+      this._root = _root || this;
+
+      this._read();
+    }
+    Flags.prototype._read = function() {
+      this.cwr = this._io.readBitsIntBe(1) != 0;
+      this.ece = this._io.readBitsIntBe(1) != 0;
+      this.urg = this._io.readBitsIntBe(1) != 0;
+      this.ack = this._io.readBitsIntBe(1) != 0;
+      this.psh = this._io.readBitsIntBe(1) != 0;
+      this.rst = this._io.readBitsIntBe(1) != 0;
+      this.syn = this._io.readBitsIntBe(1) != 0;
+      this.fin = this._io.readBitsIntBe(1) != 0;
+    }
+
+    /**
+     * Congestion Window Reduced
+     */
+
+    /**
+     * ECN-Echo
+     */
+
+    /**
+     * Urgent pointer field is significant
+     */
+
+    /**
+     * Acknowledgment field is significant
+     */
+
+    /**
+     * Push function
+     */
+
+    /**
+     * Reset the connection
+     */
+
+    /**
+     * Synchronize sequence numbers
+     */
+
+    /**
+     * No more data from sender
+     */
+
+    Flags.prototype.toString = function() {
+      return (this.cwr ? "|CWR" : "") + (this.ece ? "|ECE" : "") + (this.urg ? "|URG" : "") + (this.ack ? "|ACK" : "") + (this.psh ? "|PSH" : "") + (this.rst ? "|RST" : "") + (this.syn ? "|SYN" : "") + (this.fin ? "|FIN" : "");
+    }
+
+    return Flags;
+  })();
+
+  /**
+   * Source port
+   */
+
+  /**
+   * Destination port
+   */
+
+  /**
+   * Sequence number
+   */
+
+  /**
+   * Acknowledgment number
+   */
+
+  /**
+   * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+   */
+
   return TcpSegment;
 })();
 return TcpSegment;
diff --git a/tcp_segment/src/lua/tcp_segment.lua b/tcp_segment/src/lua/tcp_segment.lua
index 9e832f58e..e700b9003 100644
--- a/tcp_segment/src/lua/tcp_segment.lua
+++ b/tcp_segment/src/lua/tcp_segment.lua
@@ -24,12 +24,66 @@ function TcpSegment:_read()
   self.dst_port = self._io:read_u2be()
   self.seq_num = self._io:read_u4be()
   self.ack_num = self._io:read_u4be()
-  self.b12 = self._io:read_u1()
-  self.b13 = self._io:read_u1()
+  self.data_offset = self._io:read_bits_int_be(4)
+  self.reserved = self._io:read_bits_int_be(4)
+  self._io:align_to_byte()
+  self.flags = TcpSegment.Flags(self._io, self, self._root)
   self.window_size = self._io:read_u2be()
   self.checksum = self._io:read_u2be()
   self.urgent_pointer = self._io:read_u2be()
+  if ((self.data_offset * 4) - 20) ~= 0 then
+    self.options = self._io:read_bytes(((self.data_offset * 4) - 20))
+  end
   self.body = self._io:read_bytes_full()
 end
 
+-- 
+-- Source port.
+-- 
+-- Destination port.
+-- 
+-- Sequence number.
+-- 
+-- Acknowledgment number.
+-- 
+-- Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present).
+
+-- 
+-- TCP header flags as defined "TCP Header Flags" registry.
+TcpSegment.Flags = class.class(KaitaiStruct)
+
+function TcpSegment.Flags:_init(io, parent, root)
+  KaitaiStruct._init(self, io)
+  self._parent = parent
+  self._root = root or self
+  self:_read()
+end
+
+function TcpSegment.Flags:_read()
+  self.cwr = self._io:read_bits_int_be(1) ~= 0
+  self.ece = self._io:read_bits_int_be(1) ~= 0
+  self.urg = self._io:read_bits_int_be(1) ~= 0
+  self.ack = self._io:read_bits_int_be(1) ~= 0
+  self.psh = self._io:read_bits_int_be(1) ~= 0
+  self.rst = self._io:read_bits_int_be(1) ~= 0
+  self.syn = self._io:read_bits_int_be(1) ~= 0
+  self.fin = self._io:read_bits_int_be(1) ~= 0
+end
+
+-- 
+-- Congestion Window Reduced.
+-- 
+-- ECN-Echo.
+-- 
+-- Urgent pointer field is significant.
+-- 
+-- Acknowledgment field is significant.
+-- 
+-- Push function.
+-- 
+-- Reset the connection.
+-- 
+-- Synchronize sequence numbers.
+-- 
+-- No more data from sender.
 
diff --git a/tcp_segment/src/nim/tcp_segment.nim b/tcp_segment/src/nim/tcp_segment.nim
index de38c67a2..6cf65c046 100644
--- a/tcp_segment/src/nim/tcp_segment.nim
+++ b/tcp_segment/src/nim/tcp_segment.nim
@@ -7,15 +7,28 @@ type
     `dstPort`*: uint16
     `seqNum`*: uint32
     `ackNum`*: uint32
-    `b12`*: uint8
-    `b13`*: uint8
+    `dataOffset`*: uint64
+    `reserved`*: uint64
+    `flags`*: TcpSegment_Flags
     `windowSize`*: uint16
     `checksum`*: uint16
     `urgentPointer`*: uint16
+    `options`*: seq[byte]
     `body`*: seq[byte]
     `parent`*: KaitaiStruct
+  TcpSegment_Flags* = ref object of KaitaiStruct
+    `cwr`*: bool
+    `ece`*: bool
+    `urg`*: bool
+    `ack`*: bool
+    `psh`*: bool
+    `rst`*: bool
+    `syn`*: bool
+    `fin`*: bool
+    `parent`*: TcpSegment
 
 proc read*(_: typedesc[TcpSegment], io: KaitaiStream, root: KaitaiStruct, parent: KaitaiStruct): TcpSegment
+proc read*(_: typedesc[TcpSegment_Flags], io: KaitaiStream, root: KaitaiStruct, parent: TcpSegment): TcpSegment_Flags
 
 
 
@@ -34,27 +47,118 @@ proc read*(_: typedesc[TcpSegment], io: KaitaiStream, root: KaitaiStruct, parent
   this.root = root
   this.parent = parent
 
+
+  ##[
+  Source port
+  ]##
   let srcPortExpr = this.io.readU2be()
   this.srcPort = srcPortExpr
+
+  ##[
+  Destination port
+  ]##
   let dstPortExpr = this.io.readU2be()
   this.dstPort = dstPortExpr
+
+  ##[
+  Sequence number
+  ]##
   let seqNumExpr = this.io.readU4be()
   this.seqNum = seqNumExpr
+
+  ##[
+  Acknowledgment number
+  ]##
   let ackNumExpr = this.io.readU4be()
   this.ackNum = ackNumExpr
-  let b12Expr = this.io.readU1()
-  this.b12 = b12Expr
-  let b13Expr = this.io.readU1()
-  this.b13 = b13Expr
+
+  ##[
+  Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+  ]##
+  let dataOffsetExpr = this.io.readBitsIntBe(4)
+  this.dataOffset = dataOffsetExpr
+  let reservedExpr = this.io.readBitsIntBe(4)
+  this.reserved = reservedExpr
+  alignToByte(this.io)
+  let flagsExpr = TcpSegment_Flags.read(this.io, this.root, this)
+  this.flags = flagsExpr
   let windowSizeExpr = this.io.readU2be()
   this.windowSize = windowSizeExpr
   let checksumExpr = this.io.readU2be()
   this.checksum = checksumExpr
   let urgentPointerExpr = this.io.readU2be()
   this.urgentPointer = urgentPointerExpr
+  if ((this.dataOffset * 4) - 20) != 0:
+    let optionsExpr = this.io.readBytes(int(((this.dataOffset * 4) - 20)))
+    this.options = optionsExpr
   let bodyExpr = this.io.readBytesFull()
   this.body = bodyExpr
 
 proc fromFile*(_: typedesc[TcpSegment], filename: string): TcpSegment =
   TcpSegment.read(newKaitaiFileStream(filename), nil, nil)
 
+
+##[
+TCP header flags as defined "TCP Header Flags" registry.
+
+]##
+proc read*(_: typedesc[TcpSegment_Flags], io: KaitaiStream, root: KaitaiStruct, parent: TcpSegment): TcpSegment_Flags =
+  template this: untyped = result
+  this = new(TcpSegment_Flags)
+  let root = if root == nil: cast[TcpSegment](this) else: cast[TcpSegment](root)
+  this.io = io
+  this.root = root
+  this.parent = parent
+
+
+  ##[
+  Congestion Window Reduced
+  ]##
+  let cwrExpr = this.io.readBitsIntBe(1) != 0
+  this.cwr = cwrExpr
+
+  ##[
+  ECN-Echo
+  ]##
+  let eceExpr = this.io.readBitsIntBe(1) != 0
+  this.ece = eceExpr
+
+  ##[
+  Urgent pointer field is significant
+  ]##
+  let urgExpr = this.io.readBitsIntBe(1) != 0
+  this.urg = urgExpr
+
+  ##[
+  Acknowledgment field is significant
+  ]##
+  let ackExpr = this.io.readBitsIntBe(1) != 0
+  this.ack = ackExpr
+
+  ##[
+  Push function
+  ]##
+  let pshExpr = this.io.readBitsIntBe(1) != 0
+  this.psh = pshExpr
+
+  ##[
+  Reset the connection
+  ]##
+  let rstExpr = this.io.readBitsIntBe(1) != 0
+  this.rst = rstExpr
+
+  ##[
+  Synchronize sequence numbers
+  ]##
+  let synExpr = this.io.readBitsIntBe(1) != 0
+  this.syn = synExpr
+
+  ##[
+  No more data from sender
+  ]##
+  let finExpr = this.io.readBitsIntBe(1) != 0
+  this.fin = finExpr
+
+proc fromFile*(_: typedesc[TcpSegment_Flags], filename: string): TcpSegment_Flags =
+  TcpSegment_Flags.read(newKaitaiFileStream(filename), nil, nil)
+
diff --git a/tcp_segment/src/perl/TcpSegment.pm b/tcp_segment/src/perl/TcpSegment.pm
index c5d81a988..86f3f6133 100644
--- a/tcp_segment/src/perl/TcpSegment.pm
+++ b/tcp_segment/src/perl/TcpSegment.pm
@@ -38,11 +38,16 @@ sub _read {
     $self->{dst_port} = $self->{_io}->read_u2be();
     $self->{seq_num} = $self->{_io}->read_u4be();
     $self->{ack_num} = $self->{_io}->read_u4be();
-    $self->{b12} = $self->{_io}->read_u1();
-    $self->{b13} = $self->{_io}->read_u1();
+    $self->{data_offset} = $self->{_io}->read_bits_int_be(4);
+    $self->{reserved} = $self->{_io}->read_bits_int_be(4);
+    $self->{_io}->align_to_byte();
+    $self->{flags} = TcpSegment::Flags->new($self->{_io}, $self, $self->{_root});
     $self->{window_size} = $self->{_io}->read_u2be();
     $self->{checksum} = $self->{_io}->read_u2be();
     $self->{urgent_pointer} = $self->{_io}->read_u2be();
+    if ((($self->data_offset() * 4) - 20) != 0) {
+        $self->{options} = $self->{_io}->read_bytes((($self->data_offset() * 4) - 20));
+    }
     $self->{body} = $self->{_io}->read_bytes_full();
 }
 
@@ -66,14 +71,19 @@ sub ack_num {
     return $self->{ack_num};
 }
 
-sub b12 {
+sub data_offset {
     my ($self) = @_;
-    return $self->{b12};
+    return $self->{data_offset};
 }
 
-sub b13 {
+sub reserved {
     my ($self) = @_;
-    return $self->{b13};
+    return $self->{reserved};
+}
+
+sub flags {
+    my ($self) = @_;
+    return $self->{flags};
 }
 
 sub window_size {
@@ -91,9 +101,94 @@ sub urgent_pointer {
     return $self->{urgent_pointer};
 }
 
+sub options {
+    my ($self) = @_;
+    return $self->{options};
+}
+
 sub body {
     my ($self) = @_;
     return $self->{body};
 }
 
+########################################################################
+package TcpSegment::Flags;
+
+our @ISA = 'IO::KaitaiStruct::Struct';
+
+sub from_file {
+    my ($class, $filename) = @_;
+    my $fd;
+
+    open($fd, '<', $filename) or return undef;
+    binmode($fd);
+    return new($class, IO::KaitaiStruct::Stream->new($fd));
+}
+
+sub new {
+    my ($class, $_io, $_parent, $_root) = @_;
+    my $self = IO::KaitaiStruct::Struct->new($_io);
+
+    bless $self, $class;
+    $self->{_parent} = $_parent;
+    $self->{_root} = $_root || $self;;
+
+    $self->_read();
+
+    return $self;
+}
+
+sub _read {
+    my ($self) = @_;
+
+    $self->{cwr} = $self->{_io}->read_bits_int_be(1);
+    $self->{ece} = $self->{_io}->read_bits_int_be(1);
+    $self->{urg} = $self->{_io}->read_bits_int_be(1);
+    $self->{ack} = $self->{_io}->read_bits_int_be(1);
+    $self->{psh} = $self->{_io}->read_bits_int_be(1);
+    $self->{rst} = $self->{_io}->read_bits_int_be(1);
+    $self->{syn} = $self->{_io}->read_bits_int_be(1);
+    $self->{fin} = $self->{_io}->read_bits_int_be(1);
+}
+
+sub cwr {
+    my ($self) = @_;
+    return $self->{cwr};
+}
+
+sub ece {
+    my ($self) = @_;
+    return $self->{ece};
+}
+
+sub urg {
+    my ($self) = @_;
+    return $self->{urg};
+}
+
+sub ack {
+    my ($self) = @_;
+    return $self->{ack};
+}
+
+sub psh {
+    my ($self) = @_;
+    return $self->{psh};
+}
+
+sub rst {
+    my ($self) = @_;
+    return $self->{rst};
+}
+
+sub syn {
+    my ($self) = @_;
+    return $self->{syn};
+}
+
+sub fin {
+    my ($self) = @_;
+    return $self->{fin};
+}
+
 1;
diff --git a/tcp_segment/src/php/TcpSegment.php b/tcp_segment/src/php/TcpSegment.php
index 2106ff510..7fb8a5dce 100644
--- a/tcp_segment/src/php/TcpSegment.php
+++ b/tcp_segment/src/php/TcpSegment.php
@@ -20,32 +20,133 @@ private function _read() {
             $this->_m_dstPort = $this->_io->readU2be();
             $this->_m_seqNum = $this->_io->readU4be();
             $this->_m_ackNum = $this->_io->readU4be();
-            $this->_m_b12 = $this->_io->readU1();
-            $this->_m_b13 = $this->_io->readU1();
+            $this->_m_dataOffset = $this->_io->readBitsIntBe(4);
+            $this->_m_reserved = $this->_io->readBitsIntBe(4);
+            $this->_io->alignToByte();
+            $this->_m_flags = new \TcpSegment\Flags($this->_io, $this, $this->_root);
             $this->_m_windowSize = $this->_io->readU2be();
             $this->_m_checksum = $this->_io->readU2be();
             $this->_m_urgentPointer = $this->_io->readU2be();
+            if ((($this->dataOffset() * 4) - 20) != 0) {
+                $this->_m_options = $this->_io->readBytes((($this->dataOffset() * 4) - 20));
+            }
             $this->_m_body = $this->_io->readBytesFull();
         }
         protected $_m_srcPort;
         protected $_m_dstPort;
         protected $_m_seqNum;
         protected $_m_ackNum;
-        protected $_m_b12;
-        protected $_m_b13;
+        protected $_m_dataOffset;
+        protected $_m_reserved;
+        protected $_m_flags;
         protected $_m_windowSize;
         protected $_m_checksum;
         protected $_m_urgentPointer;
+        protected $_m_options;
         protected $_m_body;
+
+        /**
+         * Source port
+         */
         public function srcPort() { return $this->_m_srcPort; }
+
+        /**
+         * Destination port
+         */
         public function dstPort() { return $this->_m_dstPort; }
+
+        /**
+         * Sequence number
+         */
         public function seqNum() { return $this->_m_seqNum; }
+
+        /**
+         * Acknowledgment number
+         */
         public function ackNum() { return $this->_m_ackNum; }
-        public function b12() { return $this->_m_b12; }
-        public function b13() { return $this->_m_b13; }
+
+        /**
+         * Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+         */
+        public function dataOffset() { return $this->_m_dataOffset; }
+        public function reserved() { return $this->_m_reserved; }
+        public function flags() { return $this->_m_flags; }
         public function windowSize() { return $this->_m_windowSize; }
         public function checksum() { return $this->_m_checksum; }
         public function urgentPointer() { return $this->_m_urgentPointer; }
+        public function options() { return $this->_m_options; }
         public function body() { return $this->_m_body; }
     }
 }
+
+/**
+ * TCP header flags as defined "TCP Header Flags" registry.
+ */
+
+namespace TcpSegment {
+    class Flags extends \Kaitai\Struct\Struct {
+        public function __construct(\Kaitai\Struct\Stream $_io, \TcpSegment $_parent = null, \TcpSegment $_root = null) {
+            parent::__construct($_io, $_parent, $_root);
+            $this->_read();
+        }
+
+        private function _read() {
+            $this->_m_cwr = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_ece = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_urg = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_ack = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_psh = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_rst = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_syn = $this->_io->readBitsIntBe(1) != 0;
+            $this->_m_fin = $this->_io->readBitsIntBe(1) != 0;
+        }
+        protected $_m_cwr;
+        protected $_m_ece;
+        protected $_m_urg;
+        protected $_m_ack;
+        protected $_m_psh;
+        protected $_m_rst;
+        protected $_m_syn;
+        protected $_m_fin;
+
+        /**
+         * Congestion Window Reduced
+         */
+        public function cwr() { return $this->_m_cwr; }
+
+        /**
+         * ECN-Echo
+         */
+        public function ece() { return $this->_m_ece; }
+
+        /**
+         * Urgent pointer field is significant
+         */
+        public function urg() { return $this->_m_urg; }
+
+        /**
+         * Acknowledgment field is significant
+         */
+        public function ack() { return $this->_m_ack; }
+
+        /**
+         * Push function
+         */
+        public function psh() { return $this->_m_psh; }
+
+        /**
+         * Reset the connection
+         */
+        public function rst() { return $this->_m_rst; }
+
+        /**
+         * Synchronize sequence numbers
+         */
+        public function syn() { return $this->_m_syn; }
+
+        /**
+         * No more data from sender
+         */
+        public function fin() { return $this->_m_fin; }
+    }
+}
diff --git a/tcp_segment/src/python/tcp_segment.py b/tcp_segment/src/python/tcp_segment.py
index 6fb19177f..5a3b043fd 100644
--- a/tcp_segment/src/python/tcp_segment.py
+++ b/tcp_segment/src/python/tcp_segment.py
@@ -24,11 +24,39 @@ def _read(self):
         self.dst_port = self._io.read_u2be()
         self.seq_num = self._io.read_u4be()
         self.ack_num = self._io.read_u4be()
-        self.b12 = self._io.read_u1()
-        self.b13 = self._io.read_u1()
+        self.data_offset = self._io.read_bits_int_be(4)
+        self.reserved = self._io.read_bits_int_be(4)
+        self._io.align_to_byte()
+        self.flags = TcpSegment.Flags(self._io, self, self._root)
         self.window_size = self._io.read_u2be()
         self.checksum = self._io.read_u2be()
         self.urgent_pointer = self._io.read_u2be()
+        if ((self.data_offset * 4) - 20) != 0:
+            self.options = self._io.read_bytes(((self.data_offset * 4) - 20))
+
         self.body = self._io.read_bytes_full()
 
+    class Flags(KaitaiStruct):
+        """TCP header flags as defined "TCP Header Flags" registry.
+        """
+        def __init__(self, _io, _parent=None, _root=None):
+            self._io = _io
+            self._parent = _parent
+            self._root = _root if _root else self
+            self._read()
+
+        def _read(self):
+            self.cwr = self._io.read_bits_int_be(1) != 0
+            self.ece = self._io.read_bits_int_be(1) != 0
+            self.urg = self._io.read_bits_int_be(1) != 0
+            self.ack = self._io.read_bits_int_be(1) != 0
+            self.psh = self._io.read_bits_int_be(1) != 0
+            self.rst = self._io.read_bits_int_be(1) != 0
+            self.syn = self._io.read_bits_int_be(1) != 0
+            self.fin = self._io.read_bits_int_be(1) != 0
+
+
+        def __repr__(self):
+            return (u"|CWR" if self.cwr else u"") + (u"|ECE" if self.ece else u"") + (u"|URG" if self.urg else u"") + (u"|ACK" if self.ack else u"") + (u"|PSH" if self.psh else u"") + (u"|RST" if self.rst else u"") + (u"|SYN" if self.syn else u"") + (u"|FIN" if self.fin else u"")
+
 
diff --git a/tcp_segment/src/ruby/tcp_segment.rb b/tcp_segment/src/ruby/tcp_segment.rb
index 80bb5425c..4c302fe8e 100644
--- a/tcp_segment/src/ruby/tcp_segment.rb
+++ b/tcp_segment/src/ruby/tcp_segment.rb
@@ -23,22 +23,101 @@ def _read
     @dst_port = @_io.read_u2be
     @seq_num = @_io.read_u4be
     @ack_num = @_io.read_u4be
-    @b12 = @_io.read_u1
-    @b13 = @_io.read_u1
+    @data_offset = @_io.read_bits_int_be(4)
+    @reserved = @_io.read_bits_int_be(4)
+    @_io.align_to_byte
+    @flags = Flags.new(@_io, self, @_root)
     @window_size = @_io.read_u2be
     @checksum = @_io.read_u2be
     @urgent_pointer = @_io.read_u2be
+    if ((data_offset * 4) - 20) != 0
+      @options = @_io.read_bytes(((data_offset * 4) - 20))
+    end
     @body = @_io.read_bytes_full
     self
   end
+
+  ##
+  # TCP header flags as defined "TCP Header Flags" registry.
+  class Flags < Kaitai::Struct::Struct
+    def initialize(_io, _parent = nil, _root = self)
+      super(_io, _parent, _root)
+      _read
+    end
+
+    def _read
+      @cwr = @_io.read_bits_int_be(1) != 0
+      @ece = @_io.read_bits_int_be(1) != 0
+      @urg = @_io.read_bits_int_be(1) != 0
+      @ack = @_io.read_bits_int_be(1) != 0
+      @psh = @_io.read_bits_int_be(1) != 0
+      @rst = @_io.read_bits_int_be(1) != 0
+      @syn = @_io.read_bits_int_be(1) != 0
+      @fin = @_io.read_bits_int_be(1) != 0
+      self
+    end
+
+    ##
+    # Congestion Window Reduced
+    attr_reader :cwr
+
+    ##
+    # ECN-Echo
+    attr_reader :ece
+
+    ##
+    # Urgent pointer field is significant
+    attr_reader :urg
+
+    ##
+    # Acknowledgment field is significant
+    attr_reader :ack
+
+    ##
+    # Push function
+    attr_reader :psh
+
+    ##
+    # Reset the connection
+    attr_reader :rst
+
+    ##
+    # Synchronize sequence numbers
+    attr_reader :syn
+
+    ##
+    # No more data from sender
+    attr_reader :fin
+
+    def inspect
+      (cwr ? "|CWR" : "") + (ece ? "|ECE" : "") + (urg ? "|URG" : "") + (ack ? "|ACK" : "") + (psh ? "|PSH" : "") + (rst ? "|RST" : "") + (syn ? "|SYN" : "") + (fin ? "|FIN" : "")
+    end
+  end
+
+  ##
+  # Source port
   attr_reader :src_port
+
+  ##
+  # Destination port
   attr_reader :dst_port
+
+  ##
+  # Sequence number
   attr_reader :seq_num
+
+  ##
+  # Acknowledgment number
   attr_reader :ack_num
-  attr_reader :b12
-  attr_reader :b13
+
+  ##
+  # Data offset (in 32-bit words from the beginning of this type, normally 32 or can be extended if there are any TCP options or padding is present)
+  attr_reader :data_offset
+  attr_reader :reserved
+  attr_reader :flags
   attr_reader :window_size
   attr_reader :checksum
   attr_reader :urgent_pointer
+  attr_reader :options
   attr_reader :body
 end
diff --git a/tcp_segment/tcp_segment.svg b/tcp_segment/tcp_segment.svg
index cddf291ba..785dbfb50 100644
--- a/tcp_segment/tcp_segment.svg
+++ b/tcp_segment/tcp_segment.svg
@@ -4,110 +4,222 @@
 <!-- Generated by graphviz version 2.43.0 (0)
  -->
 <!-- Title: %3 Pages: 1 -->
-<svg width="276pt" height="302pt"
- viewBox="0.00 0.00 276.00 302.00" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-<g id="graph0" class="graph" transform="scale(1 1) rotate(0) translate(4 298)">
+<svg width="757pt" height="363pt"
+ viewBox="0.00 0.00 757.00 363.00" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+<g id="graph0" class="graph" transform="scale(1 1) rotate(0) translate(4 359)">
 <title>%3</title>
-<polygon fill="white" stroke="transparent" points="-4,4 -4,-298 272,-298 272,4 -4,4"/>
+<polygon fill="white" stroke="transparent" points="-4,4 -4,-359 753,-359 753,4 -4,4"/>
 <g id="clust1" class="cluster">
 <title>cluster__tcp_segment</title>
-<polygon fill="none" stroke="black" stroke-dasharray="1,5" points="8,-8 8,-286 260,-286 260,-8 8,-8"/>
-<text text-anchor="middle" x="134" y="-270.8" font-family="Times,serif" font-size="14.00">TcpSegment</text>
+<polygon fill="none" stroke="black" stroke-dasharray="1,5" points="8,-8 8,-347 741,-347 741,-8 8,-8"/>
+<text text-anchor="middle" x="374.5" y="-331.8" font-family="Times,serif" font-size="14.00">TcpSegment</text>
+</g>
+<g id="clust2" class="cluster">
+<title>cluster__flags</title>
+<polygon fill="none" stroke="black" stroke-dasharray="1,5" points="419,-28 419,-265 733,-265 733,-28 419,-28"/>
+<text text-anchor="middle" x="576" y="-249.8" font-family="Times,serif" font-size="14.00">TcpSegment::Flags</text>
 </g>
 <!-- tcp_segment__seq -->
 <g id="node1" class="node">
 <title>tcp_segment__seq</title>
-<polygon fill="#e0ffe0" stroke="transparent" points="24,-229 24,-250 55,-250 55,-229 24,-229"/>
-<polygon fill="none" stroke="black" points="24,-229 24,-250 55,-250 55,-229 24,-229"/>
-<text text-anchor="start" x="27" y="-235.8" font-family="Times,serif" font-size="14.00">pos</text>
-<polygon fill="#e0ffe0" stroke="transparent" points="55,-229 55,-250 89,-250 89,-229 55,-229"/>
-<polygon fill="none" stroke="black" points="55,-229 55,-250 89,-250 89,-229 55,-229"/>
-<text text-anchor="start" x="58" y="-235.8" font-family="Times,serif" font-size="14.00">size</text>
-<polygon fill="#e0ffe0" stroke="transparent" points="89,-229 89,-250 131,-250 131,-229 89,-229"/>
-<polygon fill="none" stroke="black" points="89,-229 89,-250 131,-250 131,-229 89,-229"/>
-<text text-anchor="start" x="94" y="-235.8" font-family="Times,serif" font-size="14.00">type</text>
-<polygon fill="#e0ffe0" stroke="transparent" points="131,-229 131,-250 244,-250 244,-229 131,-229"/>
-<polygon fill="none" stroke="black" points="131,-229 131,-250 244,-250 244,-229 131,-229"/>
-<text text-anchor="start" x="180.5" y="-235.8" font-family="Times,serif" font-size="14.00">id</text>
-<polygon fill="none" stroke="black" points="24,-208 24,-229 55,-229 55,-208 24,-208"/>
-<text text-anchor="start" x="34.5" y="-214.8" font-family="Times,serif" font-size="14.00">0</text>
-<polygon fill="none" stroke="black" points="55,-208 55,-229 89,-229 89,-208 55,-208"/>
-<text text-anchor="start" x="67" y="-214.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="89,-208 89,-229 131,-229 131,-208 89,-208"/>
-<text text-anchor="start" x="92" y="-214.8" font-family="Times,serif" font-size="14.00">u2be</text>
-<polygon fill="none" stroke="black" points="131,-208 131,-229 244,-229 244,-208 131,-208"/>
-<text text-anchor="start" x="158" y="-214.8" font-family="Times,serif" font-size="14.00">src_port</text>
-<polygon fill="none" stroke="black" points="24,-187 24,-208 55,-208 55,-187 24,-187"/>
-<text text-anchor="start" x="34.5" y="-193.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="55,-187 55,-208 89,-208 89,-187 55,-187"/>
-<text text-anchor="start" x="67" y="-193.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="89,-187 89,-208 131,-208 131,-187 89,-187"/>
-<text text-anchor="start" x="92" y="-193.8" font-family="Times,serif" font-size="14.00">u2be</text>
-<polygon fill="none" stroke="black" points="131,-187 131,-208 244,-208 244,-187 131,-187"/>
-<text text-anchor="start" x="157.5" y="-193.8" font-family="Times,serif" font-size="14.00">dst_port</text>
-<polygon fill="none" stroke="black" points="24,-166 24,-187 55,-187 55,-166 24,-166"/>
-<text text-anchor="start" x="34.5" y="-172.8" font-family="Times,serif" font-size="14.00">4</text>
-<polygon fill="none" stroke="black" points="55,-166 55,-187 89,-187 89,-166 55,-166"/>
-<text text-anchor="start" x="67" y="-172.8" font-family="Times,serif" font-size="14.00">4</text>
-<polygon fill="none" stroke="black" points="89,-166 89,-187 131,-187 131,-166 89,-166"/>
-<text text-anchor="start" x="92" y="-172.8" font-family="Times,serif" font-size="14.00">u4be</text>
-<polygon fill="none" stroke="black" points="131,-166 131,-187 244,-187 244,-166 131,-166"/>
-<text text-anchor="start" x="155.5" y="-172.8" font-family="Times,serif" font-size="14.00">seq_num</text>
-<polygon fill="none" stroke="black" points="24,-145 24,-166 55,-166 55,-145 24,-145"/>
-<text text-anchor="start" x="34.5" y="-151.8" font-family="Times,serif" font-size="14.00">8</text>
-<polygon fill="none" stroke="black" points="55,-145 55,-166 89,-166 89,-145 55,-145"/>
-<text text-anchor="start" x="67" y="-151.8" font-family="Times,serif" font-size="14.00">4</text>
-<polygon fill="none" stroke="black" points="89,-145 89,-166 131,-166 131,-145 89,-145"/>
-<text text-anchor="start" x="92" y="-151.8" font-family="Times,serif" font-size="14.00">u4be</text>
-<polygon fill="none" stroke="black" points="131,-145 131,-166 244,-166 244,-145 131,-145"/>
-<text text-anchor="start" x="156" y="-151.8" font-family="Times,serif" font-size="14.00">ack_num</text>
-<polygon fill="none" stroke="black" points="24,-124 24,-145 55,-145 55,-124 24,-124"/>
-<text text-anchor="start" x="30" y="-130.8" font-family="Times,serif" font-size="14.00">12</text>
-<polygon fill="none" stroke="black" points="55,-124 55,-145 89,-145 89,-124 55,-124"/>
-<text text-anchor="start" x="67" y="-130.8" font-family="Times,serif" font-size="14.00">1</text>
-<polygon fill="none" stroke="black" points="89,-124 89,-145 131,-145 131,-124 89,-124"/>
-<text text-anchor="start" x="100.5" y="-130.8" font-family="Times,serif" font-size="14.00">u1</text>
-<polygon fill="none" stroke="black" points="131,-124 131,-145 244,-145 244,-124 131,-124"/>
-<text text-anchor="start" x="173.5" y="-130.8" font-family="Times,serif" font-size="14.00">b12</text>
-<polygon fill="none" stroke="black" points="24,-103 24,-124 55,-124 55,-103 24,-103"/>
-<text text-anchor="start" x="30" y="-109.8" font-family="Times,serif" font-size="14.00">13</text>
-<polygon fill="none" stroke="black" points="55,-103 55,-124 89,-124 89,-103 55,-103"/>
-<text text-anchor="start" x="67" y="-109.8" font-family="Times,serif" font-size="14.00">1</text>
-<polygon fill="none" stroke="black" points="89,-103 89,-124 131,-124 131,-103 89,-103"/>
-<text text-anchor="start" x="100.5" y="-109.8" font-family="Times,serif" font-size="14.00">u1</text>
-<polygon fill="none" stroke="black" points="131,-103 131,-124 244,-124 244,-103 131,-103"/>
-<text text-anchor="start" x="173.5" y="-109.8" font-family="Times,serif" font-size="14.00">b13</text>
-<polygon fill="none" stroke="black" points="24,-82 24,-103 55,-103 55,-82 24,-82"/>
-<text text-anchor="start" x="30" y="-88.8" font-family="Times,serif" font-size="14.00">14</text>
-<polygon fill="none" stroke="black" points="55,-82 55,-103 89,-103 89,-82 55,-82"/>
-<text text-anchor="start" x="67" y="-88.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="89,-82 89,-103 131,-103 131,-82 89,-82"/>
-<text text-anchor="start" x="92" y="-88.8" font-family="Times,serif" font-size="14.00">u2be</text>
-<polygon fill="none" stroke="black" points="131,-82 131,-103 244,-103 244,-82 131,-82"/>
-<text text-anchor="start" x="142.5" y="-88.8" font-family="Times,serif" font-size="14.00">window_size</text>
-<polygon fill="none" stroke="black" points="24,-61 24,-82 55,-82 55,-61 24,-61"/>
-<text text-anchor="start" x="30" y="-67.8" font-family="Times,serif" font-size="14.00">16</text>
-<polygon fill="none" stroke="black" points="55,-61 55,-82 89,-82 89,-61 55,-61"/>
-<text text-anchor="start" x="67" y="-67.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="89,-61 89,-82 131,-82 131,-61 89,-61"/>
-<text text-anchor="start" x="92" y="-67.8" font-family="Times,serif" font-size="14.00">u2be</text>
-<polygon fill="none" stroke="black" points="131,-61 131,-82 244,-82 244,-61 131,-61"/>
-<text text-anchor="start" x="152" y="-67.8" font-family="Times,serif" font-size="14.00">checksum</text>
-<polygon fill="none" stroke="black" points="24,-40 24,-61 55,-61 55,-40 24,-40"/>
-<text text-anchor="start" x="30" y="-46.8" font-family="Times,serif" font-size="14.00">18</text>
-<polygon fill="none" stroke="black" points="55,-40 55,-61 89,-61 89,-40 55,-40"/>
-<text text-anchor="start" x="67" y="-46.8" font-family="Times,serif" font-size="14.00">2</text>
-<polygon fill="none" stroke="black" points="89,-40 89,-61 131,-61 131,-40 89,-40"/>
-<text text-anchor="start" x="92" y="-46.8" font-family="Times,serif" font-size="14.00">u2be</text>
-<polygon fill="none" stroke="black" points="131,-40 131,-61 244,-61 244,-40 131,-40"/>
-<text text-anchor="start" x="134" y="-46.8" font-family="Times,serif" font-size="14.00">urgent_pointer</text>
-<polygon fill="none" stroke="black" points="24,-19 24,-40 55,-40 55,-19 24,-19"/>
-<text text-anchor="start" x="30" y="-25.8" font-family="Times,serif" font-size="14.00">20</text>
-<polygon fill="none" stroke="black" points="55,-19 55,-40 89,-40 89,-19 55,-19"/>
-<text text-anchor="start" x="65.5" y="-25.8" font-family="Times,serif" font-size="14.00">⇲</text>
-<polygon fill="none" stroke="black" points="89,-19 89,-40 131,-40 131,-19 89,-19"/>
-<polygon fill="none" stroke="black" points="131,-19 131,-40 244,-40 244,-19 131,-19"/>
-<text text-anchor="start" x="170" y="-25.8" font-family="Times,serif" font-size="14.00">body</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="24.5,-272 24.5,-293 62.5,-293 62.5,-272 24.5,-272"/>
+<polygon fill="none" stroke="black" points="24.5,-272 24.5,-293 62.5,-293 62.5,-272 24.5,-272"/>
+<text text-anchor="start" x="31" y="-278.8" font-family="Times,serif" font-size="14.00">pos</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="62.5,-272 62.5,-293 224.5,-293 224.5,-272 62.5,-272"/>
+<polygon fill="none" stroke="black" points="62.5,-272 62.5,-293 224.5,-293 224.5,-272 62.5,-272"/>
+<text text-anchor="start" x="129.5" y="-278.8" font-family="Times,serif" font-size="14.00">size</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="224.5,-272 224.5,-293 270.5,-293 270.5,-272 224.5,-272"/>
+<polygon fill="none" stroke="black" points="224.5,-272 224.5,-293 270.5,-293 270.5,-272 224.5,-272"/>
+<text text-anchor="start" x="231.5" y="-278.8" font-family="Times,serif" font-size="14.00">type</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="270.5,-272 270.5,-293 383.5,-293 383.5,-272 270.5,-272"/>
+<polygon fill="none" stroke="black" points="270.5,-272 270.5,-293 383.5,-293 383.5,-272 270.5,-272"/>
+<text text-anchor="start" x="320" y="-278.8" font-family="Times,serif" font-size="14.00">id</text>
+<polygon fill="none" stroke="black" points="24.5,-251 24.5,-272 62.5,-272 62.5,-251 24.5,-251"/>
+<text text-anchor="start" x="38.5" y="-257.8" font-family="Times,serif" font-size="14.00">0</text>
+<polygon fill="none" stroke="black" points="62.5,-251 62.5,-272 224.5,-272 224.5,-251 62.5,-251"/>
+<text text-anchor="start" x="138.5" y="-257.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="224.5,-251 224.5,-272 270.5,-272 270.5,-251 224.5,-251"/>
+<text text-anchor="start" x="229.5" y="-257.8" font-family="Times,serif" font-size="14.00">u2be</text>
+<polygon fill="none" stroke="black" points="270.5,-251 270.5,-272 383.5,-272 383.5,-251 270.5,-251"/>
+<text text-anchor="start" x="297.5" y="-257.8" font-family="Times,serif" font-size="14.00">src_port</text>
+<polygon fill="none" stroke="black" points="24.5,-230 24.5,-251 62.5,-251 62.5,-230 24.5,-230"/>
+<text text-anchor="start" x="38.5" y="-236.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="62.5,-230 62.5,-251 224.5,-251 224.5,-230 62.5,-230"/>
+<text text-anchor="start" x="138.5" y="-236.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="224.5,-230 224.5,-251 270.5,-251 270.5,-230 224.5,-230"/>
+<text text-anchor="start" x="229.5" y="-236.8" font-family="Times,serif" font-size="14.00">u2be</text>
+<polygon fill="none" stroke="black" points="270.5,-230 270.5,-251 383.5,-251 383.5,-230 270.5,-230"/>
+<text text-anchor="start" x="297" y="-236.8" font-family="Times,serif" font-size="14.00">dst_port</text>
+<polygon fill="none" stroke="black" points="24.5,-209 24.5,-230 62.5,-230 62.5,-209 24.5,-209"/>
+<text text-anchor="start" x="38.5" y="-215.8" font-family="Times,serif" font-size="14.00">4</text>
+<polygon fill="none" stroke="black" points="62.5,-209 62.5,-230 224.5,-230 224.5,-209 62.5,-209"/>
+<text text-anchor="start" x="138.5" y="-215.8" font-family="Times,serif" font-size="14.00">4</text>
+<polygon fill="none" stroke="black" points="224.5,-209 224.5,-230 270.5,-230 270.5,-209 224.5,-209"/>
+<text text-anchor="start" x="229.5" y="-215.8" font-family="Times,serif" font-size="14.00">u4be</text>
+<polygon fill="none" stroke="black" points="270.5,-209 270.5,-230 383.5,-230 383.5,-209 270.5,-209"/>
+<text text-anchor="start" x="295" y="-215.8" font-family="Times,serif" font-size="14.00">seq_num</text>
+<polygon fill="none" stroke="black" points="24.5,-188 24.5,-209 62.5,-209 62.5,-188 24.5,-188"/>
+<text text-anchor="start" x="38.5" y="-194.8" font-family="Times,serif" font-size="14.00">8</text>
+<polygon fill="none" stroke="black" points="62.5,-188 62.5,-209 224.5,-209 224.5,-188 62.5,-188"/>
+<text text-anchor="start" x="138.5" y="-194.8" font-family="Times,serif" font-size="14.00">4</text>
+<polygon fill="none" stroke="black" points="224.5,-188 224.5,-209 270.5,-209 270.5,-188 224.5,-188"/>
+<text text-anchor="start" x="229.5" y="-194.8" font-family="Times,serif" font-size="14.00">u4be</text>
+<polygon fill="none" stroke="black" points="270.5,-188 270.5,-209 383.5,-209 383.5,-188 270.5,-188"/>
+<text text-anchor="start" x="295.5" y="-194.8" font-family="Times,serif" font-size="14.00">ack_num</text>
+<polygon fill="none" stroke="black" points="24.5,-167 24.5,-188 62.5,-188 62.5,-167 24.5,-167"/>
+<text text-anchor="start" x="34" y="-173.8" font-family="Times,serif" font-size="14.00">12</text>
+<polygon fill="none" stroke="black" points="62.5,-167 62.5,-188 224.5,-188 224.5,-167 62.5,-167"/>
+<text text-anchor="start" x="134" y="-173.8" font-family="Times,serif" font-size="14.00">4b</text>
+<polygon fill="none" stroke="black" points="224.5,-167 224.5,-188 270.5,-188 270.5,-167 224.5,-167"/>
+<text text-anchor="start" x="238" y="-173.8" font-family="Times,serif" font-size="14.00">b4</text>
+<polygon fill="none" stroke="black" points="270.5,-167 270.5,-188 383.5,-188 383.5,-167 270.5,-167"/>
+<text text-anchor="start" x="287.5" y="-173.8" font-family="Times,serif" font-size="14.00">data_offset</text>
+<polygon fill="none" stroke="black" points="24.5,-146 24.5,-167 62.5,-167 62.5,-146 24.5,-146"/>
+<text text-anchor="start" x="27.5" y="-152.8" font-family="Times,serif" font-size="14.00">12:4</text>
+<polygon fill="none" stroke="black" points="62.5,-146 62.5,-167 224.5,-167 224.5,-146 62.5,-146"/>
+<text text-anchor="start" x="134" y="-152.8" font-family="Times,serif" font-size="14.00">4b</text>
+<polygon fill="none" stroke="black" points="224.5,-146 224.5,-167 270.5,-167 270.5,-146 224.5,-146"/>
+<text text-anchor="start" x="238" y="-152.8" font-family="Times,serif" font-size="14.00">b4</text>
+<polygon fill="none" stroke="black" points="270.5,-146 270.5,-167 383.5,-167 383.5,-146 270.5,-146"/>
+<text text-anchor="start" x="295" y="-152.8" font-family="Times,serif" font-size="14.00">reserved</text>
+<polygon fill="none" stroke="black" points="24.5,-125 24.5,-146 62.5,-146 62.5,-125 24.5,-125"/>
+<text text-anchor="start" x="34" y="-131.8" font-family="Times,serif" font-size="14.00">13</text>
+<polygon fill="none" stroke="black" points="62.5,-125 62.5,-146 224.5,-146 224.5,-125 62.5,-125"/>
+<text text-anchor="start" x="138.5" y="-131.8" font-family="Times,serif" font-size="14.00">1</text>
+<polygon fill="none" stroke="black" points="224.5,-125 224.5,-146 270.5,-146 270.5,-125 224.5,-125"/>
+<text text-anchor="start" x="227.5" y="-131.8" font-family="Times,serif" font-size="14.00">Flags</text>
+<polygon fill="none" stroke="black" points="270.5,-125 270.5,-146 383.5,-146 383.5,-125 270.5,-125"/>
+<text text-anchor="start" x="310" y="-131.8" font-family="Times,serif" font-size="14.00">flags</text>
+<polygon fill="none" stroke="black" points="24.5,-104 24.5,-125 62.5,-125 62.5,-104 24.5,-104"/>
+<text text-anchor="start" x="34" y="-110.8" font-family="Times,serif" font-size="14.00">14</text>
+<polygon fill="none" stroke="black" points="62.5,-104 62.5,-125 224.5,-125 224.5,-104 62.5,-104"/>
+<text text-anchor="start" x="138.5" y="-110.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="224.5,-104 224.5,-125 270.5,-125 270.5,-104 224.5,-104"/>
+<text text-anchor="start" x="229.5" y="-110.8" font-family="Times,serif" font-size="14.00">u2be</text>
+<polygon fill="none" stroke="black" points="270.5,-104 270.5,-125 383.5,-125 383.5,-104 270.5,-104"/>
+<text text-anchor="start" x="282" y="-110.8" font-family="Times,serif" font-size="14.00">window_size</text>
+<polygon fill="none" stroke="black" points="24.5,-83 24.5,-104 62.5,-104 62.5,-83 24.5,-83"/>
+<text text-anchor="start" x="34" y="-89.8" font-family="Times,serif" font-size="14.00">16</text>
+<polygon fill="none" stroke="black" points="62.5,-83 62.5,-104 224.5,-104 224.5,-83 62.5,-83"/>
+<text text-anchor="start" x="138.5" y="-89.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="224.5,-83 224.5,-104 270.5,-104 270.5,-83 224.5,-83"/>
+<text text-anchor="start" x="229.5" y="-89.8" font-family="Times,serif" font-size="14.00">u2be</text>
+<polygon fill="none" stroke="black" points="270.5,-83 270.5,-104 383.5,-104 383.5,-83 270.5,-83"/>
+<text text-anchor="start" x="291.5" y="-89.8" font-family="Times,serif" font-size="14.00">checksum</text>
+<polygon fill="none" stroke="black" points="24.5,-62 24.5,-83 62.5,-83 62.5,-62 24.5,-62"/>
+<text text-anchor="start" x="34" y="-68.8" font-family="Times,serif" font-size="14.00">18</text>
+<polygon fill="none" stroke="black" points="62.5,-62 62.5,-83 224.5,-83 224.5,-62 62.5,-62"/>
+<text text-anchor="start" x="138.5" y="-68.8" font-family="Times,serif" font-size="14.00">2</text>
+<polygon fill="none" stroke="black" points="224.5,-62 224.5,-83 270.5,-83 270.5,-62 224.5,-62"/>
+<text text-anchor="start" x="229.5" y="-68.8" font-family="Times,serif" font-size="14.00">u2be</text>
+<polygon fill="none" stroke="black" points="270.5,-62 270.5,-83 383.5,-83 383.5,-62 270.5,-62"/>
+<text text-anchor="start" x="273.5" y="-68.8" font-family="Times,serif" font-size="14.00">urgent_pointer</text>
+<polygon fill="none" stroke="black" points="24.5,-41 24.5,-62 62.5,-62 62.5,-41 24.5,-41"/>
+<text text-anchor="start" x="34" y="-47.8" font-family="Times,serif" font-size="14.00">20</text>
+<polygon fill="none" stroke="black" points="62.5,-41 62.5,-62 224.5,-62 224.5,-41 62.5,-41"/>
+<text text-anchor="start" x="65.5" y="-47.8" font-family="Times,serif" font-size="14.00">((data_offset * 4) &#45; 20)</text>
+<polygon fill="none" stroke="black" points="224.5,-41 224.5,-62 270.5,-62 270.5,-41 224.5,-41"/>
+<polygon fill="none" stroke="black" points="270.5,-41 270.5,-62 383.5,-62 383.5,-41 270.5,-41"/>
+<text text-anchor="start" x="300.5" y="-47.8" font-family="Times,serif" font-size="14.00">options</text>
+<polygon fill="none" stroke="black" points="24.5,-20 24.5,-41 62.5,-41 62.5,-20 24.5,-20"/>
+<text text-anchor="start" x="36.5" y="-26.8" font-family="Times,serif" font-size="14.00">...</text>
+<polygon fill="none" stroke="black" points="62.5,-20 62.5,-41 224.5,-41 224.5,-20 62.5,-20"/>
+<text text-anchor="start" x="137" y="-26.8" font-family="Times,serif" font-size="14.00">⇲</text>
+<polygon fill="none" stroke="black" points="224.5,-20 224.5,-41 270.5,-41 270.5,-20 224.5,-20"/>
+<polygon fill="none" stroke="black" points="270.5,-20 270.5,-41 383.5,-41 383.5,-20 270.5,-20"/>
+<text text-anchor="start" x="309.5" y="-26.8" font-family="Times,serif" font-size="14.00">body</text>
+</g>
+<!-- tcp_segment__seq&#45;&gt;tcp_segment__seq -->
+<g id="edge2" class="edge">
+<title>tcp_segment__seq:data_offset_type&#45;&gt;tcp_segment__seq:options_size</title>
+<path fill="none" stroke="#404040" d="M343.83,-188.25C419.78,-241.09 408.94,-315.5 235.5,-315.5 67.47,-315.5 52.06,-140.89 120.32,-69.26"/>
+<polygon fill="#404040" stroke="#404040" points="122.84,-71.7 127.65,-62.26 118,-66.64 122.84,-71.7"/>
+</g>
+<!-- flags__seq -->
+<g id="node2" class="node">
+<title>flags__seq</title>
+<polygon fill="#e0ffe0" stroke="transparent" points="435,-208 435,-229 466,-229 466,-208 435,-208"/>
+<polygon fill="none" stroke="black" points="435,-208 435,-229 466,-229 466,-208 435,-208"/>
+<text text-anchor="start" x="438" y="-214.8" font-family="Times,serif" font-size="14.00">pos</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="466,-208 466,-229 500,-229 500,-208 466,-208"/>
+<polygon fill="none" stroke="black" points="466,-208 466,-229 500,-229 500,-208 466,-208"/>
+<text text-anchor="start" x="469" y="-214.8" font-family="Times,serif" font-size="14.00">size</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="500,-208 500,-229 684,-229 684,-208 500,-208"/>
+<polygon fill="none" stroke="black" points="500,-208 500,-229 684,-229 684,-208 500,-208"/>
+<text text-anchor="start" x="576" y="-214.8" font-family="Times,serif" font-size="14.00">type</text>
+<polygon fill="#e0ffe0" stroke="transparent" points="684,-208 684,-229 717,-229 717,-208 684,-208"/>
+<polygon fill="none" stroke="black" points="684,-208 684,-229 717,-229 717,-208 684,-208"/>
+<text text-anchor="start" x="693.5" y="-214.8" font-family="Times,serif" font-size="14.00">id</text>
+<polygon fill="none" stroke="black" points="435,-187 435,-208 466,-208 466,-187 435,-187"/>
+<text text-anchor="start" x="445.5" y="-193.8" font-family="Times,serif" font-size="14.00">0</text>
+<polygon fill="none" stroke="black" points="466,-187 466,-208 500,-208 500,-187 466,-187"/>
+<text text-anchor="start" x="473.5" y="-193.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-187 500,-208 684,-208 684,-187 500,-187"/>
+<text text-anchor="start" x="503" y="-193.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-187 684,-208 717,-208 717,-187 684,-187"/>
+<text text-anchor="start" x="687" y="-193.8" font-family="Times,serif" font-size="14.00">cwr</text>
+<polygon fill="none" stroke="black" points="435,-166 435,-187 466,-187 466,-166 435,-166"/>
+<text text-anchor="start" x="439" y="-172.8" font-family="Times,serif" font-size="14.00">0:1</text>
+<polygon fill="none" stroke="black" points="466,-166 466,-187 500,-187 500,-166 466,-166"/>
+<text text-anchor="start" x="473.5" y="-172.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-166 500,-187 684,-187 684,-166 500,-166"/>
+<text text-anchor="start" x="503" y="-172.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-166 684,-187 717,-187 717,-166 684,-166"/>
+<text text-anchor="start" x="688" y="-172.8" font-family="Times,serif" font-size="14.00">ece</text>
+<polygon fill="none" stroke="black" points="435,-145 435,-166 466,-166 466,-145 435,-145"/>
+<text text-anchor="start" x="439" y="-151.8" font-family="Times,serif" font-size="14.00">0:2</text>
+<polygon fill="none" stroke="black" points="466,-145 466,-166 500,-166 500,-145 466,-145"/>
+<text text-anchor="start" x="473.5" y="-151.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-145 500,-166 684,-166 684,-145 500,-145"/>
+<text text-anchor="start" x="503" y="-151.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-145 684,-166 717,-166 717,-145 684,-145"/>
+<text text-anchor="start" x="688" y="-151.8" font-family="Times,serif" font-size="14.00">urg</text>
+<polygon fill="none" stroke="black" points="435,-124 435,-145 466,-145 466,-124 435,-124"/>
+<text text-anchor="start" x="439" y="-130.8" font-family="Times,serif" font-size="14.00">0:3</text>
+<polygon fill="none" stroke="black" points="466,-124 466,-145 500,-145 500,-124 466,-124"/>
+<text text-anchor="start" x="473.5" y="-130.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-124 500,-145 684,-145 684,-124 500,-124"/>
+<text text-anchor="start" x="503" y="-130.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-124 684,-145 717,-145 717,-124 684,-124"/>
+<text text-anchor="start" x="688" y="-130.8" font-family="Times,serif" font-size="14.00">ack</text>
+<polygon fill="none" stroke="black" points="435,-103 435,-124 466,-124 466,-103 435,-103"/>
+<text text-anchor="start" x="439" y="-109.8" font-family="Times,serif" font-size="14.00">0:4</text>
+<polygon fill="none" stroke="black" points="466,-103 466,-124 500,-124 500,-103 466,-103"/>
+<text text-anchor="start" x="473.5" y="-109.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-103 500,-124 684,-124 684,-103 500,-103"/>
+<text text-anchor="start" x="503" y="-109.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-103 684,-124 717,-124 717,-103 684,-103"/>
+<text text-anchor="start" x="687.5" y="-109.8" font-family="Times,serif" font-size="14.00">psh</text>
+<polygon fill="none" stroke="black" points="435,-82 435,-103 466,-103 466,-82 435,-82"/>
+<text text-anchor="start" x="439" y="-88.8" font-family="Times,serif" font-size="14.00">0:5</text>
+<polygon fill="none" stroke="black" points="466,-82 466,-103 500,-103 500,-82 466,-82"/>
+<text text-anchor="start" x="473.5" y="-88.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-82 500,-103 684,-103 684,-82 500,-82"/>
+<text text-anchor="start" x="503" y="-88.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-82 684,-103 717,-103 717,-82 684,-82"/>
+<text text-anchor="start" x="690" y="-88.8" font-family="Times,serif" font-size="14.00">rst</text>
+<polygon fill="none" stroke="black" points="435,-61 435,-82 466,-82 466,-61 435,-61"/>
+<text text-anchor="start" x="439" y="-67.8" font-family="Times,serif" font-size="14.00">0:6</text>
+<polygon fill="none" stroke="black" points="466,-61 466,-82 500,-82 500,-61 466,-61"/>
+<text text-anchor="start" x="473.5" y="-67.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-61 500,-82 684,-82 684,-61 500,-61"/>
+<text text-anchor="start" x="503" y="-67.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-61 684,-82 717,-82 717,-61 684,-61"/>
+<text text-anchor="start" x="688" y="-67.8" font-family="Times,serif" font-size="14.00">syn</text>
+<polygon fill="none" stroke="black" points="435,-40 435,-61 466,-61 466,-40 435,-40"/>
+<text text-anchor="start" x="439" y="-46.8" font-family="Times,serif" font-size="14.00">0:7</text>
+<polygon fill="none" stroke="black" points="466,-40 466,-61 500,-61 500,-40 466,-40"/>
+<text text-anchor="start" x="473.5" y="-46.8" font-family="Times,serif" font-size="14.00">1b</text>
+<polygon fill="none" stroke="black" points="500,-40 500,-61 684,-61 684,-40 500,-40"/>
+<text text-anchor="start" x="503" y="-46.8" font-family="Times,serif" font-size="14.00">BitsType1(BigBitEndian)</text>
+<polygon fill="none" stroke="black" points="684,-40 684,-61 717,-61 717,-40 684,-40"/>
+<text text-anchor="start" x="691" y="-46.8" font-family="Times,serif" font-size="14.00">fin</text>
+</g>
+<!-- tcp_segment__seq&#45;&gt;flags__seq -->
+<g id="edge1" class="edge">
+<title>tcp_segment__seq:flags_type&#45;&gt;flags__seq</title>
+<path fill="none" stroke="black" stroke-width="2" d="M384.5,-135C395.01,-135 405.84,-135 416.76,-135"/>
+<polygon fill="black" stroke="black" stroke-width="2" points="416.8,-138.5 426.8,-135 416.8,-131.5 416.8,-138.5"/>
 </g>
 </g>
 </svg>
diff --git a/tga/cpp_stl_11.html b/tga/cpp_stl_11.html
index 9a2eebec2..ed4a68603 100644
--- a/tga/cpp_stl_11.html
+++ b/tga/cpp_stl_11.html
@@ -784,7 +784,7 @@ <h3>tga.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/cpp_stl_98.html b/tga/cpp_stl_98.html
index 54b71c280..a20d0cc88 100644
--- a/tga/cpp_stl_98.html
+++ b/tga/cpp_stl_98.html
@@ -816,7 +816,7 @@ <h3>tga.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/csharp.html b/tga/csharp.html
index 60e2d12d1..30580b345 100644
--- a/tga/csharp.html
+++ b/tga/csharp.html
@@ -642,7 +642,7 @@ <h3>Tga.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/go.html b/tga/go.html
index b7664561d..abbe9ef6d 100644
--- a/tga/go.html
+++ b/tga/go.html
@@ -717,7 +717,7 @@ <h3>tga.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/graphviz.html b/tga/graphviz.html
index ddee82192..65bb74b76 100644
--- a/tga/graphviz.html
+++ b/tga/graphviz.html
@@ -358,7 +358,7 @@ <h3>tga.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/index.html b/tga/index.html
index aae90c369..68828b04c 100644
--- a/tga/index.html
+++ b/tga/index.html
@@ -411,7 +411,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/java.html b/tga/java.html
index 0ccbfdbfe..772f84f27 100644
--- a/tga/java.html
+++ b/tga/java.html
@@ -658,7 +658,7 @@ <h3>Tga.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/javascript.html b/tga/javascript.html
index a210405a1..cb9b1c890 100644
--- a/tga/javascript.html
+++ b/tga/javascript.html
@@ -546,7 +546,7 @@ <h3>Tga.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/lua.html b/tga/lua.html
index 628403fd4..d5207dd67 100644
--- a/tga/lua.html
+++ b/tga/lua.html
@@ -457,7 +457,7 @@ <h3>tga.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/nim.html b/tga/nim.html
index b2aa0f06a..d2cbe4d17 100644
--- a/tga/nim.html
+++ b/tga/nim.html
@@ -557,7 +557,7 @@ <h3>tga.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/perl.html b/tga/perl.html
index eabc212ff..44e060880 100644
--- a/tga/perl.html
+++ b/tga/perl.html
@@ -623,7 +623,7 @@ <h3>Tga.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/php.html b/tga/php.html
index 33568c8e3..c0668cc21 100644
--- a/tga/php.html
+++ b/tga/php.html
@@ -546,7 +546,7 @@ <h3>Tga.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/python.html b/tga/python.html
index 13cd94ea4..e531ba50a 100644
--- a/tga/python.html
+++ b/tga/python.html
@@ -449,7 +449,7 @@ <h3>tga.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tga/ruby.html b/tga/ruby.html
index facb29cbc..5cab35e32 100644
--- a/tga/ruby.html
+++ b/tga/ruby.html
@@ -528,7 +528,7 @@ <h3>tga.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/cpp_stl_11.html b/tls_client_hello/cpp_stl_11.html
index 437445cab..5652035e2 100644
--- a/tls_client_hello/cpp_stl_11.html
+++ b/tls_client_hello/cpp_stl_11.html
@@ -1016,7 +1016,7 @@ <h3>tls_client_hello.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/cpp_stl_98.html b/tls_client_hello/cpp_stl_98.html
index e61da4cd3..717050fc9 100644
--- a/tls_client_hello/cpp_stl_98.html
+++ b/tls_client_hello/cpp_stl_98.html
@@ -1135,7 +1135,7 @@ <h3>tls_client_hello.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/csharp.html b/tls_client_hello/csharp.html
index 7f30622fc..0d0d1bd1a 100644
--- a/tls_client_hello/csharp.html
+++ b/tls_client_hello/csharp.html
@@ -706,7 +706,7 @@ <h3>TlsClientHello.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/go.html b/tls_client_hello/go.html
index 607c84b50..79f874a86 100644
--- a/tls_client_hello/go.html
+++ b/tls_client_hello/go.html
@@ -743,7 +743,7 @@ <h3>tls_client_hello.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/graphviz.html b/tls_client_hello/graphviz.html
index 4c01d2fa0..6aba74b56 100644
--- a/tls_client_hello/graphviz.html
+++ b/tls_client_hello/graphviz.html
@@ -426,7 +426,7 @@ <h3>tls_client_hello.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/index.html b/tls_client_hello/index.html
index 78d1687a0..5f4c1149d 100644
--- a/tls_client_hello/index.html
+++ b/tls_client_hello/index.html
@@ -388,7 +388,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/java.html b/tls_client_hello/java.html
index bf4a75b7c..220cb2c63 100644
--- a/tls_client_hello/java.html
+++ b/tls_client_hello/java.html
@@ -768,7 +768,7 @@ <h3>TlsClientHello.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/javascript.html b/tls_client_hello/javascript.html
index 49066d5f8..42e3ded64 100644
--- a/tls_client_hello/javascript.html
+++ b/tls_client_hello/javascript.html
@@ -552,7 +552,7 @@ <h3>TlsClientHello.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/lua.html b/tls_client_hello/lua.html
index b176c75b9..fe01f8e2f 100644
--- a/tls_client_hello/lua.html
+++ b/tls_client_hello/lua.html
@@ -492,7 +492,7 @@ <h3>tls_client_hello.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/nim.html b/tls_client_hello/nim.html
index bc94153ce..33bc6dfa7 100644
--- a/tls_client_hello/nim.html
+++ b/tls_client_hello/nim.html
@@ -575,7 +575,7 @@ <h3>tls_client_hello.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/perl.html b/tls_client_hello/perl.html
index a669fdd6b..0150bf96e 100644
--- a/tls_client_hello/perl.html
+++ b/tls_client_hello/perl.html
@@ -873,7 +873,7 @@ <h3>TlsClientHello.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/php.html b/tls_client_hello/php.html
index 00538d868..06a937562 100644
--- a/tls_client_hello/php.html
+++ b/tls_client_hello/php.html
@@ -542,7 +542,7 @@ <h3>TlsClientHello.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/python.html b/tls_client_hello/python.html
index 492b236a6..3f401c4bb 100644
--- a/tls_client_hello/python.html
+++ b/tls_client_hello/python.html
@@ -499,7 +499,7 @@ <h3>tls_client_hello.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tls_client_hello/ruby.html b/tls_client_hello/ruby.html
index d7a358e68..476756c0f 100644
--- a/tls_client_hello/ruby.html
+++ b/tls_client_hello/ruby.html
@@ -531,7 +531,7 @@ <h3>tls_client_hello.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/cpp_stl_11.html b/tr_dos_image/cpp_stl_11.html
index 80863d637..e072b2731 100644
--- a/tr_dos_image/cpp_stl_11.html
+++ b/tr_dos_image/cpp_stl_11.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -1017,7 +1017,7 @@ <h3>tr_dos_image.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/cpp_stl_98.html b/tr_dos_image/cpp_stl_98.html
index b7599a197..40297fafb 100644
--- a/tr_dos_image/cpp_stl_98.html
+++ b/tr_dos_image/cpp_stl_98.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -1085,7 +1085,7 @@ <h3>tr_dos_image.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/csharp.html b/tr_dos_image/csharp.html
index 74fffa904..c3164bb3f 100644
--- a/tr_dos_image/csharp.html
+++ b/tr_dos_image/csharp.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -789,7 +789,7 @@ <h3>TrDosImage.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/go.html b/tr_dos_image/go.html
index 9c9b93f16..a863e7efc 100644
--- a/tr_dos_image/go.html
+++ b/tr_dos_image/go.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -867,7 +867,7 @@ <h3>tr_dos_image.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/graphviz.html b/tr_dos_image/graphviz.html
index fd461e2c7..70e5cb214 100644
--- a/tr_dos_image/graphviz.html
+++ b/tr_dos_image/graphviz.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>tr_dos_image.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/index.html b/tr_dos_image/index.html
index 9207cd93b..0236b5c97 100644
--- a/tr_dos_image/index.html
+++ b/tr_dos_image/index.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -436,7 +436,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/java.html b/tr_dos_image/java.html
index 54950a9b7..f3c0444dc 100644
--- a/tr_dos_image/java.html
+++ b/tr_dos_image/java.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -797,7 +797,7 @@ <h3>TrDosImage.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/javascript.html b/tr_dos_image/javascript.html
index b6275b146..5503502a7 100644
--- a/tr_dos_image/javascript.html
+++ b/tr_dos_image/javascript.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -624,7 +624,7 @@ <h3>TrDosImage.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/lua.html b/tr_dos_image/lua.html
index a843f9d83..082d3eaa5 100644
--- a/tr_dos_image/lua.html
+++ b/tr_dos_image/lua.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -573,7 +573,7 @@ <h3>tr_dos_image.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/nim.html b/tr_dos_image/nim.html
index 828ab4c12..111041ed9 100644
--- a/tr_dos_image/nim.html
+++ b/tr_dos_image/nim.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -661,7 +661,7 @@ <h3>tr_dos_image.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/perl.html b/tr_dos_image/perl.html
index 5f360b166..71c18ccbb 100644
--- a/tr_dos_image/perl.html
+++ b/tr_dos_image/perl.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -825,7 +825,7 @@ <h3>TrDosImage.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/php.html b/tr_dos_image/php.html
index 4a0e82ab7..89cbc9bfd 100644
--- a/tr_dos_image/php.html
+++ b/tr_dos_image/php.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -613,7 +613,7 @@ <h3>TrDosImage.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/python.html b/tr_dos_image/python.html
index 9fdf46ad9..a62d2f115 100644
--- a/tr_dos_image/python.html
+++ b/tr_dos_image/python.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -564,7 +564,7 @@ <h3>tr_dos_image.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tr_dos_image/ruby.html b/tr_dos_image/ruby.html
index d7109cd2c..35cd5d81f 100644
--- a/tr_dos_image/ruby.html
+++ b/tr_dos_image/ruby.html
@@ -105,19 +105,19 @@ <h1>TR-DOS flat-file disk image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are
-headerless and contain consequent &quot;logical tracks&quot;, each logical track
+                <p><p>.trd file is a raw dump of TR-DOS (ZX-Spectrum) floppy. .trd files are<br />
+headerless and contain consequent &quot;logical tracks&quot;, each logical track<br />
 consists of 16 256-byte sectors.</p>
-<p>Logical tracks are defined the same way as used by TR-DOS: for single-side
-floppies it's just a physical track number, for two-side floppies sides are
+<p>Logical tracks are defined the same way as used by TR-DOS: for single-side<br />
+floppies it's just a physical track number, for two-side floppies sides are<br />
 interleaved, i.e. logical_track_num = (physical_track_num &lt;&lt; 1) | side</p>
-<p>So, this format definition is more for TR-DOS filesystem than for .trd files,
+<p>So, this format definition is more for TR-DOS filesystem than for .trd files,<br />
 which are formatless.</p>
-<p>Strings (file names, disk label, disk password) are padded with spaces and use
-ZX Spectrum character set, including UDGs, block drawing chars and Basic
-tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)
+<p>Strings (file names, disk label, disk password) are padded with spaces and use<br />
+ZX Spectrum character set, including UDGs, block drawing chars and Basic<br />
+tokens. ASCII range is mostly standard ASCII, with few characters (^, `, DEL)<br />
 replaced with (up arrow, pound, copyright symbol).</p>
-<p>.trd file can be smaller than actual floppy disk, if last logical tracks are
+<p>.trd file can be smaller than actual floppy disk, if last logical tracks are<br />
 empty (contain no file data) they can be omitted.</p>
 </p>
             </div>
@@ -586,7 +586,7 @@ <h3>tr_dos_image.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/cpp_stl_11.html b/tsm/cpp_stl_11.html
index 9d5e02bd4..f64189a4a 100644
--- a/tsm/cpp_stl_11.html
+++ b/tsm/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -775,7 +775,7 @@ <h3>tsm.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/cpp_stl_98.html b/tsm/cpp_stl_98.html
index a5631bd25..bcba59da0 100644
--- a/tsm/cpp_stl_98.html
+++ b/tsm/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -834,7 +834,7 @@ <h3>tsm.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/csharp.html b/tsm/csharp.html
index d5c1a6b95..8ff4931dc 100644
--- a/tsm/csharp.html
+++ b/tsm/csharp.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -590,7 +590,7 @@ <h3>Tsm.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/go.html b/tsm/go.html
index e73ea6ae4..56a957a89 100644
--- a/tsm/go.html
+++ b/tsm/go.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -615,7 +615,7 @@ <h3>tsm.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/graphviz.html b/tsm/graphviz.html
index 76959c2ac..f3e4fba63 100644
--- a/tsm/graphviz.html
+++ b/tsm/graphviz.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -381,7 +381,7 @@ <h3>tsm.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/index.html b/tsm/index.html
index eea8a8ae1..2c9801884 100644
--- a/tsm/index.html
+++ b/tsm/index.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -363,7 +363,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/java.html b/tsm/java.html
index dfc387544..68c65f614 100644
--- a/tsm/java.html
+++ b/tsm/java.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -602,7 +602,7 @@ <h3>Tsm.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/javascript.html b/tsm/javascript.html
index a5a3557ba..850825ddb 100644
--- a/tsm/javascript.html
+++ b/tsm/javascript.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -497,7 +497,7 @@ <h3>Tsm.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/lua.html b/tsm/lua.html
index 00d1e96a9..1791a7a9a 100644
--- a/tsm/lua.html
+++ b/tsm/lua.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -453,7 +453,7 @@ <h3>tsm.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/nim.html b/tsm/nim.html
index c8dc333fa..0ee6ef360 100644
--- a/tsm/nim.html
+++ b/tsm/nim.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -493,7 +493,7 @@ <h3>tsm.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/perl.html b/tsm/perl.html
index c896f2760..5406df25f 100644
--- a/tsm/perl.html
+++ b/tsm/perl.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -619,7 +619,7 @@ <h3>Tsm.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/php.html b/tsm/php.html
index e38e718f4..dec1218c9 100644
--- a/tsm/php.html
+++ b/tsm/php.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -464,7 +464,7 @@ <h3>Tsm.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/python.html b/tsm/python.html
index 00dfbac69..f3b79441a 100644
--- a/tsm/python.html
+++ b/tsm/python.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -471,7 +471,7 @@ <h3>tsm.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/tsm/ruby.html b/tsm/ruby.html
index 16aa62818..76f27c173 100644
--- a/tsm/ruby.html
+++ b/tsm/ruby.html
@@ -105,12 +105,12 @@ <h1>InfluxDB TSM file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>InfluxDB is a scalable database optimized for storage of time
-series, real-time application metrics, operations monitoring events,
+                <p><p>InfluxDB is a scalable database optimized for storage of time<br />
+series, real-time application metrics, operations monitoring events,<br />
 etc, written in Go.</p>
-<p>Data is stored in .tsm files, which are kept pretty simple
-conceptually. Each .tsm file contains a header and footer, which
-stores offset to an index. Index is used to find a data block for a
+<p>Data is stored in .tsm files, which are kept pretty simple<br />
+conceptually. Each .tsm file contains a header and footer, which<br />
+stores offset to an index. Index is used to find a data block for a<br />
 requested time boundary.</p>
 </p>
             </div>
@@ -475,7 +475,7 @@ <h3>tsm.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/cpp_stl_11.html b/ttf/cpp_stl_11.html
index 8fba36d01..bb3634c64 100644
--- a/ttf/cpp_stl_11.html
+++ b/ttf/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -3519,7 +3519,7 @@ <h3>ttf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/cpp_stl_98.html b/ttf/cpp_stl_98.html
index 156e08bb7..b1c6fcabe 100644
--- a/ttf/cpp_stl_98.html
+++ b/ttf/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -3857,7 +3857,7 @@ <h3>ttf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/csharp.html b/ttf/csharp.html
index ef07c5bce..8c262db82 100644
--- a/ttf/csharp.html
+++ b/ttf/csharp.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -2730,7 +2730,7 @@ <h3>Ttf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/go.html b/ttf/go.html
index f8aaf7d5a..738cf56aa 100644
--- a/ttf/go.html
+++ b/ttf/go.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -3644,7 +3644,7 @@ <h3>ttf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/graphviz.html b/ttf/graphviz.html
index 577176559..17141b69f 100644
--- a/ttf/graphviz.html
+++ b/ttf/graphviz.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -987,7 +987,7 @@ <h3>ttf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/index.html b/ttf/index.html
index 9da36aa55..65068abc3 100644
--- a/ttf/index.html
+++ b/ttf/index.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -1277,7 +1277,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/java.html b/ttf/java.html
index 1d2807212..ab53a5050 100644
--- a/ttf/java.html
+++ b/ttf/java.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -3019,7 +3019,7 @@ <h3>Ttf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/javascript.html b/ttf/javascript.html
index 5d9853671..fc02b0ac8 100644
--- a/ttf/javascript.html
+++ b/ttf/javascript.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -1989,7 +1989,7 @@ <h3>Ttf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/lua.html b/ttf/lua.html
index baf5feb01..97f025be4 100644
--- a/ttf/lua.html
+++ b/ttf/lua.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -1610,7 +1610,7 @@ <h3>ttf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/nim.html b/ttf/nim.html
index 34e2bb238..68daeaecb 100644
--- a/ttf/nim.html
+++ b/ttf/nim.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -2337,7 +2337,7 @@ <h3>ttf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/perl.html b/ttf/perl.html
index 347635a68..23be7a972 100644
--- a/ttf/perl.html
+++ b/ttf/perl.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -3583,7 +3583,7 @@ <h3>Ttf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/php.html b/ttf/php.html
index 66549013c..4d7d46635 100644
--- a/ttf/php.html
+++ b/ttf/php.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -2313,7 +2313,7 @@ <h3>Ttf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/python.html b/ttf/python.html
index 0ca249861..7adeb0da9 100644
--- a/ttf/python.html
+++ b/ttf/python.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -1415,7 +1415,7 @@ <h3>ttf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/ttf/ruby.html b/ttf/ruby.html
index f27f19fed..9bd774d2b 100644
--- a/ttf/ruby.html
+++ b/ttf/ruby.html
@@ -105,7 +105,7 @@ <h1>TrueType Font File:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A TrueType font file contains data, in table format, that comprises
+                <p><p>A TrueType font file contains data, in table format, that comprises<br />
 an outline font.</p>
 </p>
             </div>
@@ -1876,7 +1876,7 @@ <h3>ttf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/cpp_stl_11.html b/udp_datagram/cpp_stl_11.html
index 82e822c0c..f5416c9e0 100644
--- a/udp_datagram/cpp_stl_11.html
+++ b/udp_datagram/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>udp_datagram.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/cpp_stl_98.html b/udp_datagram/cpp_stl_98.html
index 8d4f919c9..eb861cbf7 100644
--- a/udp_datagram/cpp_stl_98.html
+++ b/udp_datagram/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -450,7 +450,7 @@ <h3>udp_datagram.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/csharp.html b/udp_datagram/csharp.html
index 125b26e99..eb02eaeea 100644
--- a/udp_datagram/csharp.html
+++ b/udp_datagram/csharp.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -365,7 +365,7 @@ <h3>UdpDatagram.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/go.html b/udp_datagram/go.html
index b07887689..e68f3ff47 100644
--- a/udp_datagram/go.html
+++ b/udp_datagram/go.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -332,7 +332,7 @@ <h3>udp_datagram.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/graphviz.html b/udp_datagram/graphviz.html
index 0cca7c76c..c08aa156d 100644
--- a/udp_datagram/graphviz.html
+++ b/udp_datagram/graphviz.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -291,7 +291,7 @@ <h3>udp_datagram.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/index.html b/udp_datagram/index.html
index 2ed99c84a..a1c521630 100644
--- a/udp_datagram/index.html
+++ b/udp_datagram/index.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -284,7 +284,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/java.html b/udp_datagram/java.html
index 1d0cd8660..b4f3efd74 100644
--- a/udp_datagram/java.html
+++ b/udp_datagram/java.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -372,7 +372,7 @@ <h3>UdpDatagram.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/javascript.html b/udp_datagram/javascript.html
index 4a023d901..08d77a914 100644
--- a/udp_datagram/javascript.html
+++ b/udp_datagram/javascript.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -350,7 +350,7 @@ <h3>UdpDatagram.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/lua.html b/udp_datagram/lua.html
index 88856b57f..40b1fd0e1 100644
--- a/udp_datagram/lua.html
+++ b/udp_datagram/lua.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -301,7 +301,7 @@ <h3>udp_datagram.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/nim.html b/udp_datagram/nim.html
index 71e4d97d2..099c63f26 100644
--- a/udp_datagram/nim.html
+++ b/udp_datagram/nim.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -317,7 +317,7 @@ <h3>udp_datagram.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/perl.html b/udp_datagram/perl.html
index 06077b612..f56a085c7 100644
--- a/udp_datagram/perl.html
+++ b/udp_datagram/perl.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -342,7 +342,7 @@ <h3>UdpDatagram.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/php.html b/udp_datagram/php.html
index 5883b25d2..754aeb24d 100644
--- a/udp_datagram/php.html
+++ b/udp_datagram/php.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -309,7 +309,7 @@ <h3>UdpDatagram.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/python.html b/udp_datagram/python.html
index abfdc1ba1..0fb10d431 100644
--- a/udp_datagram/python.html
+++ b/udp_datagram/python.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -344,7 +344,7 @@ <h3>udp_datagram.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/udp_datagram/ruby.html b/udp_datagram/ruby.html
index ddf020214..2d9fe14af 100644
--- a/udp_datagram/ruby.html
+++ b/udp_datagram/ruby.html
@@ -105,9 +105,9 @@ <h1>UDP (User Datagram Protocol) datagram:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)
-protocol, one of the core Internet protocols. It provides source and
-destination ports, basic checksumming, but provides not guarantees
+                <p><p>UDP is a simple stateless transport layer (AKA OSI layer 4)<br />
+protocol, one of the core Internet protocols. It provides source and<br />
+destination ports, basic checksumming, but provides not guarantees<br />
 of delivery, order of packets, or duplicate delivery.</p>
 </p>
             </div>
@@ -349,7 +349,7 @@ <h3>udp_datagram.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/cpp_stl_11.html b/uefi_te/cpp_stl_11.html
index 8c769d255..cd5375daf 100644
--- a/uefi_te/cpp_stl_11.html
+++ b/uefi_te/cpp_stl_11.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -787,7 +787,7 @@ <h3>uefi_te.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/cpp_stl_98.html b/uefi_te/cpp_stl_98.html
index 570e7286e..2a8b07da5 100644
--- a/uefi_te/cpp_stl_98.html
+++ b/uefi_te/cpp_stl_98.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -840,7 +840,7 @@ <h3>uefi_te.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/csharp.html b/uefi_te/csharp.html
index a069a0bdf..7d74a51ac 100644
--- a/uefi_te/csharp.html
+++ b/uefi_te/csharp.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -629,7 +629,7 @@ <h3>UefiTe.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/go.html b/uefi_te/go.html
index 8287afa26..4e0429191 100644
--- a/uefi_te/go.html
+++ b/uefi_te/go.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -665,7 +665,7 @@ <h3>uefi_te.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/index.html b/uefi_te/index.html
index 4bf0c1949..98a1f9e04 100644
--- a/uefi_te/index.html
+++ b/uefi_te/index.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -511,7 +511,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/java.html b/uefi_te/java.html
index c23af5cea..aec22924e 100644
--- a/uefi_te/java.html
+++ b/uefi_te/java.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -668,7 +668,7 @@ <h3>UefiTe.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/javascript.html b/uefi_te/javascript.html
index cfcee87ca..0c21fc319 100644
--- a/uefi_te/javascript.html
+++ b/uefi_te/javascript.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -575,7 +575,7 @@ <h3>UefiTe.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/lua.html b/uefi_te/lua.html
index 5ec7bb503..2391bd3ce 100644
--- a/uefi_te/lua.html
+++ b/uefi_te/lua.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -484,7 +484,7 @@ <h3>uefi_te.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/nim.html b/uefi_te/nim.html
index a88ff5ec0..924323de0 100644
--- a/uefi_te/nim.html
+++ b/uefi_te/nim.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -539,7 +539,7 @@ <h3>uefi_te.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/perl.html b/uefi_te/perl.html
index cc3fdfbf9..def455417 100644
--- a/uefi_te/perl.html
+++ b/uefi_te/perl.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -680,7 +680,7 @@ <h3>UefiTe.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/php.html b/uefi_te/php.html
index 73b06d3a9..e9a14375a 100644
--- a/uefi_te/php.html
+++ b/uefi_te/php.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -646,7 +646,7 @@ <h3>UefiTe.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/python.html b/uefi_te/python.html
index dcbfdb131..586b4b4f0 100644
--- a/uefi_te/python.html
+++ b/uefi_te/python.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -509,7 +509,7 @@ <h3>uefi_te.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uefi_te/ruby.html b/uefi_te/ruby.html
index 90948582e..8937356f1 100644
--- a/uefi_te/ruby.html
+++ b/uefi_te/ruby.html
@@ -105,20 +105,20 @@ <h1>TE (Terse Executable) file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI
-firmware is stored in SPI flash memory, which is a chip soldered on a
-system's motherboard. UEFI firmware is very modular: it usually contains
-dozens, if not hundreds, of executables. To store all these separates files,
-the firmware is laid out in volumes using the Firmware File System (FFS), a
-file system specifically designed to store firmware images. The volumes
-contain files that are identified by GUIDs and each of these files contain
-one or more sections holding the data. One of these sections contains the
-actual executable image. Most of the executable images follow the PE format.
+                <p><p>This type of executables could be found inside the UEFI firmware. The UEFI<br />
+firmware is stored in SPI flash memory, which is a chip soldered on a<br />
+system's motherboard. UEFI firmware is very modular: it usually contains<br />
+dozens, if not hundreds, of executables. To store all these separates files,<br />
+the firmware is laid out in volumes using the Firmware File System (FFS), a<br />
+file system specifically designed to store firmware images. The volumes<br />
+contain files that are identified by GUIDs and each of these files contain<br />
+one or more sections holding the data. One of these sections contains the<br />
+actual executable image. Most of the executable images follow the PE format.<br />
 However, some of them follow the TE format.</p>
-<p>The Terse Executable (TE) image format was created as a mechanism to reduce
-the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a
-corresponding reduction of image sizes for executables running in the PI
-(Platform Initialization) Architecture environment. Reducing image size
+<p>The Terse Executable (TE) image format was created as a mechanism to reduce<br />
+the overhead of the PE/COFF headers in PE32/PE32+ images, resulting in a<br />
+corresponding reduction of image sizes for executables running in the PI<br />
+(Platform Initialization) Architecture environment. Reducing image size<br />
 provides an opportunity for use of a smaller system flash part.</p>
 <p>So the TE format is basically a stripped version of PE.</p>
 </p>
@@ -533,7 +533,7 @@ <h3>uefi_te.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/cpp_stl_11.html b/uimage/cpp_stl_11.html
index 9948b1429..534bbd658 100644
--- a/uimage/cpp_stl_11.html
+++ b/uimage/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -604,7 +604,7 @@ <h3>uimage.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/cpp_stl_98.html b/uimage/cpp_stl_98.html
index f2cd37e09..779aa841c 100644
--- a/uimage/cpp_stl_98.html
+++ b/uimage/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -621,7 +621,7 @@ <h3>uimage.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/csharp.html b/uimage/csharp.html
index 20f64fa0e..c5287b799 100644
--- a/uimage/csharp.html
+++ b/uimage/csharp.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -514,7 +514,7 @@ <h3>Uimage.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/go.html b/uimage/go.html
index 139d95560..71d617f82 100644
--- a/uimage/go.html
+++ b/uimage/go.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -507,7 +507,7 @@ <h3>uimage.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/graphviz.html b/uimage/graphviz.html
index f74f766a3..50d6e08f6 100644
--- a/uimage/graphviz.html
+++ b/uimage/graphviz.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -284,7 +284,7 @@ <h3>uimage.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/index.html b/uimage/index.html
index 8da4643fc..638fee29a 100644
--- a/uimage/index.html
+++ b/uimage/index.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/java.html b/uimage/java.html
index d64063a81..e1d393ed6 100644
--- a/uimage/java.html
+++ b/uimage/java.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -563,7 +563,7 @@ <h3>Uimage.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/javascript.html b/uimage/javascript.html
index 655e27044..d7e58807c 100644
--- a/uimage/javascript.html
+++ b/uimage/javascript.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -575,7 +575,7 @@ <h3>Uimage.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/lua.html b/uimage/lua.html
index 74891a635..652ac1a89 100644
--- a/uimage/lua.html
+++ b/uimage/lua.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -419,7 +419,7 @@ <h3>uimage.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/nim.html b/uimage/nim.html
index db7cb2f88..76dc5c4ab 100644
--- a/uimage/nim.html
+++ b/uimage/nim.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -442,7 +442,7 @@ <h3>uimage.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/perl.html b/uimage/perl.html
index 8a088d885..1491dcd29 100644
--- a/uimage/perl.html
+++ b/uimage/perl.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -512,7 +512,7 @@ <h3>Uimage.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/php.html b/uimage/php.html
index 99ae2ae22..844465238 100644
--- a/uimage/php.html
+++ b/uimage/php.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -841,7 +841,7 @@ <h3>Uimage.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/python.html b/uimage/python.html
index 85a0a605e..8f3c23703 100644
--- a/uimage/python.html
+++ b/uimage/python.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -454,7 +454,7 @@ <h3>uimage.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/uimage/ruby.html b/uimage/ruby.html
index 1da16acac..cfb30686f 100644
--- a/uimage/ruby.html
+++ b/uimage/ruby.html
@@ -105,8 +105,8 @@ <h1>U-Boot Image wrapper:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The new uImage format allows more flexibility in handling images of various
-types (kernel, ramdisk, etc.), it also enhances integrity protection of images
+                <p><p>The new uImage format allows more flexibility in handling images of various<br />
+types (kernel, ramdisk, etc.), it also enhances integrity protection of images<br />
 with sha1 and md5 checksums.</p>
 </p>
             </div>
@@ -473,7 +473,7 @@ <h3>uimage.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/cpp_stl_11.html b/utf8_string/cpp_stl_11.html
index 35b4dd8c8..e4fc632d6 100644
--- a/utf8_string/cpp_stl_11.html
+++ b/utf8_string/cpp_stl_11.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -666,7 +666,7 @@ <h3>utf8_string.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/cpp_stl_98.html b/utf8_string/cpp_stl_98.html
index 307f0a93f..73fc37d7f 100644
--- a/utf8_string/cpp_stl_98.html
+++ b/utf8_string/cpp_stl_98.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -686,7 +686,7 @@ <h3>utf8_string.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/csharp.html b/utf8_string/csharp.html
index aec1cbf7f..03d47c4aa 100644
--- a/utf8_string/csharp.html
+++ b/utf8_string/csharp.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -524,7 +524,7 @@ <h3>Utf8String.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/go.html b/utf8_string/go.html
index 1bff0db72..3383a06de 100644
--- a/utf8_string/go.html
+++ b/utf8_string/go.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -654,7 +654,7 @@ <h3>utf8_string.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/graphviz.html b/utf8_string/graphviz.html
index d8a5e7566..cde600c9d 100644
--- a/utf8_string/graphviz.html
+++ b/utf8_string/graphviz.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -374,7 +374,7 @@ <h3>utf8_string.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/index.html b/utf8_string/index.html
index 52945b50b..9e67cc041 100644
--- a/utf8_string/index.html
+++ b/utf8_string/index.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -356,7 +356,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/java.html b/utf8_string/java.html
index 593f2b13b..23c4b3b4c 100644
--- a/utf8_string/java.html
+++ b/utf8_string/java.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -496,7 +496,7 @@ <h3>Utf8String.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/javascript.html b/utf8_string/javascript.html
index 3eb9bdb23..1fb9907fa 100644
--- a/utf8_string/javascript.html
+++ b/utf8_string/javascript.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -467,7 +467,7 @@ <h3>Utf8String.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/lua.html b/utf8_string/lua.html
index 422963982..1466c7b68 100644
--- a/utf8_string/lua.html
+++ b/utf8_string/lua.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -432,7 +432,7 @@ <h3>utf8_string.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/nim.html b/utf8_string/nim.html
index d551c10a5..941848221 100644
--- a/utf8_string/nim.html
+++ b/utf8_string/nim.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h3>utf8_string.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/perl.html b/utf8_string/perl.html
index df3335814..6d9262cfc 100644
--- a/utf8_string/perl.html
+++ b/utf8_string/perl.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -443,7 +443,7 @@ <h3>Utf8String.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/php.html b/utf8_string/php.html
index f39d57799..868c0e2e9 100644
--- a/utf8_string/php.html
+++ b/utf8_string/php.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -413,7 +413,7 @@ <h3>Utf8String.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/python.html b/utf8_string/python.html
index c32965d80..6ea3836a6 100644
--- a/utf8_string/python.html
+++ b/utf8_string/python.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -456,7 +456,7 @@ <h3>utf8_string.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/utf8_string/ruby.html b/utf8_string/ruby.html
index c473b623d..363220af7 100644
--- a/utf8_string/ruby.html
+++ b/utf8_string/ruby.html
@@ -105,23 +105,23 @@ <h1>UTF-8-encoded string:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>UTF-8 is a popular character encoding scheme that allows to
-represent strings as sequence of code points defined in Unicode
+                <p><p>UTF-8 is a popular character encoding scheme that allows to<br />
+represent strings as sequence of code points defined in Unicode<br />
 standard. Its features are:</p>
 <ul>
-<li>variable width (i.e. one code point might be represented by 1 to 4
+<li>variable width (i.e. one code point might be represented by 1 to 4<br />
 bytes)</li>
 <li>backward compatiblity with ASCII</li>
-<li>basic validity checking (and thus distinguishing from other legacy
+<li>basic validity checking (and thus distinguishing from other legacy<br />
 8-bit encodings)</li>
 <li>maintaining sort order of codepoints if sorted as a byte array</li>
 </ul>
-<p>WARNING: For the vast majority of practical purposes of format
-definitions in Kaitai Struct, you'd likely NOT want to use this and
-rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use
-native string implementations, which are most likely more efficient
-and will give you native language strings, rather than an array of
-individual codepoints.  This format definition is provided mostly
+<p>WARNING: For the vast majority of practical purposes of format<br />
+definitions in Kaitai Struct, you'd likely NOT want to use this and<br />
+rather just use <code>type: str</code> with <code>encoding: utf-8</code>. That will use<br />
+native string implementations, which are most likely more efficient<br />
+and will give you native language strings, rather than an array of<br />
+individual codepoints.  This format definition is provided mostly<br />
 for educational / research purposes.</p>
 </p>
             </div>
@@ -439,7 +439,7 @@ <h3>utf8_string.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/cpp_stl_11.html b/vdi/cpp_stl_11.html
index fcca6ae22..4fe8ce045 100644
--- a/vdi/cpp_stl_11.html
+++ b/vdi/cpp_stl_11.html
@@ -1377,7 +1377,7 @@ <h3>vdi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/cpp_stl_98.html b/vdi/cpp_stl_98.html
index 9187f41de..496af7380 100644
--- a/vdi/cpp_stl_98.html
+++ b/vdi/cpp_stl_98.html
@@ -1520,7 +1520,7 @@ <h3>vdi.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/csharp.html b/vdi/csharp.html
index ba1ace6b4..472dc30d7 100644
--- a/vdi/csharp.html
+++ b/vdi/csharp.html
@@ -971,7 +971,7 @@ <h3>Vdi.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/go.html b/vdi/go.html
index 1d3d42d8b..7426b773a 100644
--- a/vdi/go.html
+++ b/vdi/go.html
@@ -1066,7 +1066,7 @@ <h3>vdi.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/graphviz.html b/vdi/graphviz.html
index c5bb5311c..6ce99f16f 100644
--- a/vdi/graphviz.html
+++ b/vdi/graphviz.html
@@ -522,7 +522,7 @@ <h3>vdi.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/index.html b/vdi/index.html
index 0e52c7621..ada84899a 100644
--- a/vdi/index.html
+++ b/vdi/index.html
@@ -522,7 +522,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/java.html b/vdi/java.html
index ee9d9d6f3..9134d0274 100644
--- a/vdi/java.html
+++ b/vdi/java.html
@@ -967,7 +967,7 @@ <h3>Vdi.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/javascript.html b/vdi/javascript.html
index 8be2fb358..95db16f39 100644
--- a/vdi/javascript.html
+++ b/vdi/javascript.html
@@ -724,7 +724,7 @@ <h3>Vdi.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/lua.html b/vdi/lua.html
index 606af5af8..06baa0f96 100644
--- a/vdi/lua.html
+++ b/vdi/lua.html
@@ -682,7 +682,7 @@ <h3>vdi.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/nim.html b/vdi/nim.html
index 23dece434..4c6e03690 100644
--- a/vdi/nim.html
+++ b/vdi/nim.html
@@ -794,7 +794,7 @@ <h3>vdi.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/perl.html b/vdi/perl.html
index b250d7a64..875ceb8e3 100644
--- a/vdi/perl.html
+++ b/vdi/perl.html
@@ -1078,7 +1078,7 @@ <h3>Vdi.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/php.html b/vdi/php.html
index 0966b1d05..8a3b91d4f 100644
--- a/vdi/php.html
+++ b/vdi/php.html
@@ -726,7 +726,7 @@ <h3>Vdi.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/python.html b/vdi/python.html
index 9617eaf05..e1732ff64 100644
--- a/vdi/python.html
+++ b/vdi/python.html
@@ -664,7 +664,7 @@ <h3>vdi.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vdi/ruby.html b/vdi/ruby.html
index 8514cce5a..9ad6410df 100644
--- a/vdi/ruby.html
+++ b/vdi/ruby.html
@@ -675,7 +675,7 @@ <h3>vdi.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/cpp_stl_11.html b/vfat/cpp_stl_11.html
index 7c6e90552..36dc707f0 100644
--- a/vfat/cpp_stl_11.html
+++ b/vfat/cpp_stl_11.html
@@ -1295,7 +1295,7 @@ <h3>vfat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/cpp_stl_98.html b/vfat/cpp_stl_98.html
index 16f9a96f6..de6cd9a02 100644
--- a/vfat/cpp_stl_98.html
+++ b/vfat/cpp_stl_98.html
@@ -1384,7 +1384,7 @@ <h3>vfat.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/csharp.html b/vfat/csharp.html
index 17860af50..042b6b409 100644
--- a/vfat/csharp.html
+++ b/vfat/csharp.html
@@ -1029,7 +1029,7 @@ <h3>Vfat.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/go.html b/vfat/go.html
index c7b199dc0..083b39e60 100644
--- a/vfat/go.html
+++ b/vfat/go.html
@@ -1180,7 +1180,7 @@ <h3>vfat.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/graphviz.html b/vfat/graphviz.html
index 1139b8573..e2ef403ca 100644
--- a/vfat/graphviz.html
+++ b/vfat/graphviz.html
@@ -472,7 +472,7 @@ <h3>vfat.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/index.html b/vfat/index.html
index b2fd3a7aa..e098f6612 100644
--- a/vfat/index.html
+++ b/vfat/index.html
@@ -586,7 +586,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/java.html b/vfat/java.html
index 8f5118cef..6820baf5a 100644
--- a/vfat/java.html
+++ b/vfat/java.html
@@ -1007,7 +1007,7 @@ <h3>Vfat.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/javascript.html b/vfat/javascript.html
index 16f5c91c8..7c9937f53 100644
--- a/vfat/javascript.html
+++ b/vfat/javascript.html
@@ -796,7 +796,7 @@ <h3>Vfat.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/lua.html b/vfat/lua.html
index 6daa63ee8..ff18cccc7 100644
--- a/vfat/lua.html
+++ b/vfat/lua.html
@@ -695,7 +695,7 @@ <h3>vfat.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/nim.html b/vfat/nim.html
index f34b10093..2fdc70e0b 100644
--- a/vfat/nim.html
+++ b/vfat/nim.html
@@ -917,7 +917,7 @@ <h3>vfat.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/perl.html b/vfat/perl.html
index 215540b14..be7acc3c0 100644
--- a/vfat/perl.html
+++ b/vfat/perl.html
@@ -972,7 +972,7 @@ <h3>Vfat.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/php.html b/vfat/php.html
index 8259c0f5f..2da17f927 100644
--- a/vfat/php.html
+++ b/vfat/php.html
@@ -832,7 +832,7 @@ <h3>Vfat.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/python.html b/vfat/python.html
index f48606567..b03cccf07 100644
--- a/vfat/python.html
+++ b/vfat/python.html
@@ -586,7 +586,7 @@ <h3>vfat.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vfat/ruby.html b/vfat/ruby.html
index b9846589b..6f5f80b15 100644
--- a/vfat/ruby.html
+++ b/vfat/ruby.html
@@ -752,7 +752,7 @@ <h3>vfat.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/cpp_stl_11.html b/vlq_base128_be/cpp_stl_11.html
index 2147925a9..bc0970300 100644
--- a/vlq_base128_be/cpp_stl_11.html
+++ b/vlq_base128_be/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -522,7 +522,7 @@ <h3>vlq_base128_be.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/cpp_stl_98.html b/vlq_base128_be/cpp_stl_98.html
index 71cf4c9da..a92dde622 100644
--- a/vlq_base128_be/cpp_stl_98.html
+++ b/vlq_base128_be/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -542,7 +542,7 @@ <h3>vlq_base128_be.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/csharp.html b/vlq_base128_be/csharp.html
index 9c416bb55..5235ee0a6 100644
--- a/vlq_base128_be/csharp.html
+++ b/vlq_base128_be/csharp.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -421,7 +421,7 @@ <h3>VlqBase128Be.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/index.html b/vlq_base128_be/index.html
index b438cb189..a09115fea 100644
--- a/vlq_base128_be/index.html
+++ b/vlq_base128_be/index.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -291,7 +291,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/java.html b/vlq_base128_be/java.html
index 215b0f454..1239d372c 100644
--- a/vlq_base128_be/java.html
+++ b/vlq_base128_be/java.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -422,7 +422,7 @@ <h3>VlqBase128Be.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/javascript.html b/vlq_base128_be/javascript.html
index 7aec10db5..977a1e936 100644
--- a/vlq_base128_be/javascript.html
+++ b/vlq_base128_be/javascript.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -388,7 +388,7 @@ <h3>VlqBase128Be.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/lua.html b/vlq_base128_be/lua.html
index a413ae595..d13fe5af0 100644
--- a/vlq_base128_be/lua.html
+++ b/vlq_base128_be/lua.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -339,7 +339,7 @@ <h3>vlq_base128_be.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/nim.html b/vlq_base128_be/nim.html
index a37361f4a..7bf43e801 100644
--- a/vlq_base128_be/nim.html
+++ b/vlq_base128_be/nim.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -359,7 +359,7 @@ <h3>vlq_base128_be.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/perl.html b/vlq_base128_be/perl.html
index 44834482b..4d7836d37 100644
--- a/vlq_base128_be/perl.html
+++ b/vlq_base128_be/perl.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -358,7 +358,7 @@ <h3>VlqBase128Be.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/php.html b/vlq_base128_be/php.html
index f455a8444..80d49319d 100644
--- a/vlq_base128_be/php.html
+++ b/vlq_base128_be/php.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -339,7 +339,7 @@ <h3>VlqBase128Be.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/python.html b/vlq_base128_be/python.html
index c87f3440f..bfdae76e6 100644
--- a/vlq_base128_be/python.html
+++ b/vlq_base128_be/python.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -366,7 +366,7 @@ <h3>vlq_base128_be.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_be/ruby.html b/vlq_base128_be/ruby.html
index 08d3c3f92..2b17dc98f 100644
--- a/vlq_base128_be/ruby.html
+++ b/vlq_base128_be/ruby.html
@@ -105,8 +105,8 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;most significant group first&quot;, i.e. in &quot;big-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
@@ -114,7 +114,7 @@ <h1>Variable length quantity, unsigned integer, base128, big-endian:
 <li>ASN.1 BER encoding</li>
 <li>RAR 5.0 file format</li>
 </ul>
-<p>More information on this encoding is available at
+<p>More information on this encoding is available at<br />
 <a href="https://en.wikipedia.org/wiki/Variable-length_quantity">https://en.wikipedia.org/wiki/Variable-length_quantity</a></p>
 <p>This particular implementation supports serialized values to up 8 bytes long.</p>
 </p>
@@ -371,7 +371,7 @@ <h3>vlq_base128_be.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/cpp_stl_11.html b/vlq_base128_le/cpp_stl_11.html
index c4704aab4..52ced5fcc 100644
--- a/vlq_base128_le/cpp_stl_11.html
+++ b/vlq_base128_le/cpp_stl_11.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -568,7 +568,7 @@ <h3>vlq_base128_le.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/cpp_stl_98.html b/vlq_base128_le/cpp_stl_98.html
index a6b0ca9e3..0abae83d5 100644
--- a/vlq_base128_le/cpp_stl_98.html
+++ b/vlq_base128_le/cpp_stl_98.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -588,7 +588,7 @@ <h3>vlq_base128_le.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/csharp.html b/vlq_base128_le/csharp.html
index 2110330cf..a8b1b4fe3 100644
--- a/vlq_base128_le/csharp.html
+++ b/vlq_base128_le/csharp.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -463,7 +463,7 @@ <h3>VlqBase128Le.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/index.html b/vlq_base128_le/index.html
index 3a0dc83e5..9e28870db 100644
--- a/vlq_base128_le/index.html
+++ b/vlq_base128_le/index.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -306,7 +306,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/java.html b/vlq_base128_le/java.html
index 4158ce5a4..aec079fd3 100644
--- a/vlq_base128_le/java.html
+++ b/vlq_base128_le/java.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -452,7 +452,7 @@ <h3>VlqBase128Le.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/javascript.html b/vlq_base128_le/javascript.html
index 81c524799..eb0515001 100644
--- a/vlq_base128_le/javascript.html
+++ b/vlq_base128_le/javascript.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -418,7 +418,7 @@ <h3>VlqBase128Le.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/lua.html b/vlq_base128_le/lua.html
index 849845c01..feb57aba0 100644
--- a/vlq_base128_le/lua.html
+++ b/vlq_base128_le/lua.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -371,7 +371,7 @@ <h3>vlq_base128_le.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/nim.html b/vlq_base128_le/nim.html
index 0958396e2..b24183ba7 100644
--- a/vlq_base128_le/nim.html
+++ b/vlq_base128_le/nim.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -395,7 +395,7 @@ <h3>vlq_base128_le.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/perl.html b/vlq_base128_le/perl.html
index 6aaee074d..5e505a758 100644
--- a/vlq_base128_le/perl.html
+++ b/vlq_base128_le/perl.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -377,7 +377,7 @@ <h3>VlqBase128Le.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/php.html b/vlq_base128_le/php.html
index 1b6916a70..d2c16ea99 100644
--- a/vlq_base128_le/php.html
+++ b/vlq_base128_le/php.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -363,7 +363,7 @@ <h3>VlqBase128Le.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/python.html b/vlq_base128_le/python.html
index e4a13d4c8..bc6076fd7 100644
--- a/vlq_base128_le/python.html
+++ b/vlq_base128_le/python.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -396,7 +396,7 @@ <h3>vlq_base128_le.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vlq_base128_le/ruby.html b/vlq_base128_le/ruby.html
index 09a32dbb3..30dddefc8 100644
--- a/vlq_base128_le/ruby.html
+++ b/vlq_base128_le/ruby.html
@@ -105,19 +105,19 @@ <h1>Variable length quantity, unsigned/signed integer, base128, little-endian:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups
-consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered
+                <p><p>A variable-length unsigned/signed integer using base128 encoding. 1-byte groups<br />
+consist of 1-bit flag of continuation and 7-bit value chunk, and are ordered<br />
 &quot;least significant group first&quot;, i.e. in &quot;little-endian&quot; manner.</p>
 <p>This particular encoding is specified and used in:</p>
 <ul>
-<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.
+<li>DWARF debug file format, where it's dubbed &quot;unsigned LEB128&quot; or &quot;ULEB128&quot;.<br />
 <a href="https://dwarfstd.org/doc/dwarf-2.0.0.pdf">https://dwarfstd.org/doc/dwarf-2.0.0.pdf</a> - page 139</li>
-<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.
+<li>Google Protocol Buffers, where it's called &quot;Base 128 Varints&quot;.<br />
 <a href="https://protobuf.dev/programming-guides/encoding/#varints">https://protobuf.dev/programming-guides/encoding/#varints</a></li>
-<li>Apache Lucene, where it's called &quot;VInt&quot;
+<li>Apache Lucene, where it's called &quot;VInt&quot;<br />
 <a href="https://lucene.apache.org/core/3_5_0/fileformats.html#VInt">https://lucene.apache.org/core/3_5_0/fileformats.html#VInt</a></li>
-<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on
-top of it for signed ints
+<li>Apache Avro uses this as a basis for integer encoding, adding ZigZag on<br />
+top of it for signed ints<br />
 <a href="https://avro.apache.org/docs/current/spec.html#binary_encode_primitive">https://avro.apache.org/docs/current/spec.html#binary_encode_primitive</a></li>
 </ul>
 <p>More information on this encoding is available at <a href="https://en.wikipedia.org/wiki/LEB128">https://en.wikipedia.org/wiki/LEB128</a></p>
@@ -394,7 +394,7 @@ <h3>vlq_base128_le.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/cpp_stl_11.html b/vmware_vmdk/cpp_stl_11.html
index e71d85945..8676a69da 100644
--- a/vmware_vmdk/cpp_stl_11.html
+++ b/vmware_vmdk/cpp_stl_11.html
@@ -654,7 +654,7 @@ <h3>vmware_vmdk.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/cpp_stl_98.html b/vmware_vmdk/cpp_stl_98.html
index b03e1117f..834b19ba9 100644
--- a/vmware_vmdk/cpp_stl_98.html
+++ b/vmware_vmdk/cpp_stl_98.html
@@ -671,7 +671,7 @@ <h3>vmware_vmdk.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/csharp.html b/vmware_vmdk/csharp.html
index 537cc8b44..a22dd762d 100644
--- a/vmware_vmdk/csharp.html
+++ b/vmware_vmdk/csharp.html
@@ -545,7 +545,7 @@ <h3>VmwareVmdk.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/go.html b/vmware_vmdk/go.html
index e97f0baf3..14d907600 100644
--- a/vmware_vmdk/go.html
+++ b/vmware_vmdk/go.html
@@ -620,7 +620,7 @@ <h3>vmware_vmdk.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/graphviz.html b/vmware_vmdk/graphviz.html
index 05dd6bae5..688617a8a 100644
--- a/vmware_vmdk/graphviz.html
+++ b/vmware_vmdk/graphviz.html
@@ -348,7 +348,7 @@ <h3>vmware_vmdk.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/index.html b/vmware_vmdk/index.html
index 52eef84e7..5af2f8bb7 100644
--- a/vmware_vmdk/index.html
+++ b/vmware_vmdk/index.html
@@ -353,7 +353,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/java.html b/vmware_vmdk/java.html
index 53c493dc8..e34f0e3ce 100644
--- a/vmware_vmdk/java.html
+++ b/vmware_vmdk/java.html
@@ -541,7 +541,7 @@ <h3>VmwareVmdk.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/javascript.html b/vmware_vmdk/javascript.html
index 9e5be8694..a67ff9a9d 100644
--- a/vmware_vmdk/javascript.html
+++ b/vmware_vmdk/javascript.html
@@ -464,7 +464,7 @@ <h3>VmwareVmdk.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/lua.html b/vmware_vmdk/lua.html
index 7750d98f5..1b2e550e7 100644
--- a/vmware_vmdk/lua.html
+++ b/vmware_vmdk/lua.html
@@ -406,7 +406,7 @@ <h3>vmware_vmdk.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/nim.html b/vmware_vmdk/nim.html
index a74ffe1a7..b25830d7d 100644
--- a/vmware_vmdk/nim.html
+++ b/vmware_vmdk/nim.html
@@ -471,7 +471,7 @@ <h3>vmware_vmdk.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/perl.html b/vmware_vmdk/perl.html
index 2051d7eae..00f8f07c5 100644
--- a/vmware_vmdk/perl.html
+++ b/vmware_vmdk/perl.html
@@ -527,7 +527,7 @@ <h3>VmwareVmdk.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/php.html b/vmware_vmdk/php.html
index 17b0c6799..010b6a663 100644
--- a/vmware_vmdk/php.html
+++ b/vmware_vmdk/php.html
@@ -444,7 +444,7 @@ <h3>VmwareVmdk.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/python.html b/vmware_vmdk/python.html
index 052627d88..63ae64d52 100644
--- a/vmware_vmdk/python.html
+++ b/vmware_vmdk/python.html
@@ -428,7 +428,7 @@ <h3>vmware_vmdk.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vmware_vmdk/ruby.html b/vmware_vmdk/ruby.html
index d2eba08f4..194802670 100644
--- a/vmware_vmdk/ruby.html
+++ b/vmware_vmdk/ruby.html
@@ -454,7 +454,7 @@ <h3>vmware_vmdk.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/cpp_stl_11.html b/vp8_ivf/cpp_stl_11.html
index 76e067b11..acf4577e6 100644
--- a/vp8_ivf/cpp_stl_11.html
+++ b/vp8_ivf/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -617,7 +617,7 @@ <h3>vp8_ivf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/cpp_stl_98.html b/vp8_ivf/cpp_stl_98.html
index d3e905cdc..aa41a6e08 100644
--- a/vp8_ivf/cpp_stl_98.html
+++ b/vp8_ivf/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -646,7 +646,7 @@ <h3>vp8_ivf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/csharp.html b/vp8_ivf/csharp.html
index 7d4744cce..9550b5ca9 100644
--- a/vp8_ivf/csharp.html
+++ b/vp8_ivf/csharp.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -504,7 +504,7 @@ <h3>Vp8Ivf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/go.html b/vp8_ivf/go.html
index f717a5fb9..f9187b4b6 100644
--- a/vp8_ivf/go.html
+++ b/vp8_ivf/go.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -495,7 +495,7 @@ <h3>vp8_ivf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/graphviz.html b/vp8_ivf/graphviz.html
index ecc78ddd6..2bfd7da85 100644
--- a/vp8_ivf/graphviz.html
+++ b/vp8_ivf/graphviz.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -332,7 +332,7 @@ <h3>vp8_ivf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/index.html b/vp8_ivf/index.html
index 8da74c3fb..c9e3d340f 100644
--- a/vp8_ivf/index.html
+++ b/vp8_ivf/index.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -342,7 +342,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/java.html b/vp8_ivf/java.html
index 2916dfc3d..5531f02a1 100644
--- a/vp8_ivf/java.html
+++ b/vp8_ivf/java.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -518,7 +518,7 @@ <h3>Vp8Ivf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/javascript.html b/vp8_ivf/javascript.html
index 38cdc6895..8dfcb5261 100644
--- a/vp8_ivf/javascript.html
+++ b/vp8_ivf/javascript.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -450,7 +450,7 @@ <h3>Vp8Ivf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/lua.html b/vp8_ivf/lua.html
index 581f003bc..3b4315140 100644
--- a/vp8_ivf/lua.html
+++ b/vp8_ivf/lua.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -380,7 +380,7 @@ <h3>vp8_ivf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/nim.html b/vp8_ivf/nim.html
index ed53839af..d8d1c2e57 100644
--- a/vp8_ivf/nim.html
+++ b/vp8_ivf/nim.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -431,7 +431,7 @@ <h3>vp8_ivf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/perl.html b/vp8_ivf/perl.html
index d69498ad8..3c6554d4b 100644
--- a/vp8_ivf/perl.html
+++ b/vp8_ivf/perl.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -481,7 +481,7 @@ <h3>Vp8Ivf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/php.html b/vp8_ivf/php.html
index 62d8beb8f..519caf416 100644
--- a/vp8_ivf/php.html
+++ b/vp8_ivf/php.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -425,7 +425,7 @@ <h3>Vp8Ivf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/python.html b/vp8_ivf/python.html
index bd60b9e22..546e33d04 100644
--- a/vp8_ivf/python.html
+++ b/vp8_ivf/python.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -395,7 +395,7 @@ <h3>vp8_ivf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/vp8_ivf/ruby.html b/vp8_ivf/ruby.html
index a2015b3cc..a8c24b8d7 100644
--- a/vp8_ivf/ruby.html
+++ b/vp8_ivf/ruby.html
@@ -105,9 +105,9 @@ <h1>VP8 raw file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>IVF is a simple container format for raw VP8 data, which is an open and
+                <p><p>IVF is a simple container format for raw VP8 data, which is an open and<br />
 royalty-free video compression format, currently developed by Google.</p>
-<p>Test .ivf files are available at
+<p>Test .ivf files are available at<br />
 <a href="https://chromium.googlesource.com/webm/vp8-test-vectors">https://chromium.googlesource.com/webm/vp8-test-vectors</a></p>
 </p>
             </div>
@@ -437,7 +437,7 @@ <h3>vp8_ivf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/cpp_stl_11.html b/warcraft_2_pud/cpp_stl_11.html
index ef077b371..5fd80ba5e 100644
--- a/warcraft_2_pud/cpp_stl_11.html
+++ b/warcraft_2_pud/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -1159,7 +1159,7 @@ <h3>warcraft_2_pud.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/cpp_stl_98.html b/warcraft_2_pud/cpp_stl_98.html
index a9b123f51..5f252a67a 100644
--- a/warcraft_2_pud/cpp_stl_98.html
+++ b/warcraft_2_pud/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -1245,7 +1245,7 @@ <h3>warcraft_2_pud.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/csharp.html b/warcraft_2_pud/csharp.html
index eb2b2dd58..d7c3ee4ec 100644
--- a/warcraft_2_pud/csharp.html
+++ b/warcraft_2_pud/csharp.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -898,7 +898,7 @@ <h3>Warcraft2Pud.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/go.html b/warcraft_2_pud/go.html
index 762b4449d..7a084c515 100644
--- a/warcraft_2_pud/go.html
+++ b/warcraft_2_pud/go.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -957,7 +957,7 @@ <h3>warcraft_2_pud.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/graphviz.html b/warcraft_2_pud/graphviz.html
index e2f6194f2..2cf866ef7 100644
--- a/warcraft_2_pud/graphviz.html
+++ b/warcraft_2_pud/graphviz.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -435,7 +435,7 @@ <h3>warcraft_2_pud.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/index.html b/warcraft_2_pud/index.html
index 408f3a121..617fb6d81 100644
--- a/warcraft_2_pud/index.html
+++ b/warcraft_2_pud/index.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -525,7 +525,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/java.html b/warcraft_2_pud/java.html
index a3ae4cbbd..97242d91d 100644
--- a/warcraft_2_pud/java.html
+++ b/warcraft_2_pud/java.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -973,7 +973,7 @@ <h3>Warcraft2Pud.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/javascript.html b/warcraft_2_pud/javascript.html
index 69b10c7ca..0623a5f9c 100644
--- a/warcraft_2_pud/javascript.html
+++ b/warcraft_2_pud/javascript.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -873,7 +873,7 @@ <h3>Warcraft2Pud.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/lua.html b/warcraft_2_pud/lua.html
index 78129f0c8..b4df35e04 100644
--- a/warcraft_2_pud/lua.html
+++ b/warcraft_2_pud/lua.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -682,7 +682,7 @@ <h3>warcraft_2_pud.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/nim.html b/warcraft_2_pud/nim.html
index 3930ee748..41f9d4115 100644
--- a/warcraft_2_pud/nim.html
+++ b/warcraft_2_pud/nim.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -763,7 +763,7 @@ <h3>warcraft_2_pud.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/perl.html b/warcraft_2_pud/perl.html
index 7be353cc0..1f4385031 100644
--- a/warcraft_2_pud/perl.html
+++ b/warcraft_2_pud/perl.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -931,7 +931,7 @@ <h3>Warcraft2Pud.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/php.html b/warcraft_2_pud/php.html
index edadca951..f18db62d7 100644
--- a/warcraft_2_pud/php.html
+++ b/warcraft_2_pud/php.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -734,7 +734,7 @@ <h3>Warcraft2Pud.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/python.html b/warcraft_2_pud/python.html
index 3c3278d29..bc69e645a 100644
--- a/warcraft_2_pud/python.html
+++ b/warcraft_2_pud/python.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -680,7 +680,7 @@ <h3>warcraft_2_pud.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/warcraft_2_pud/ruby.html b/warcraft_2_pud/ruby.html
index 29ddfb0c3..241f07fc8 100644
--- a/warcraft_2_pud/ruby.html
+++ b/warcraft_2_pud/ruby.html
@@ -105,13 +105,13 @@ <h1>Warcraft II map files:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Warcraft II game engine uses this format for map files. External
-maps can be edited by official Warcraft II map editor and saved in
-.pud files. Maps supplied with the game (i.e. single player
-campaign) follow the same format, but are instead embedded inside
+                <p><p>Warcraft II game engine uses this format for map files. External<br />
+maps can be edited by official Warcraft II map editor and saved in<br />
+.pud files. Maps supplied with the game (i.e. single player<br />
+campaign) follow the same format, but are instead embedded inside<br />
 the game container files.</p>
-<p>There are two major versions: 0x11 (original one) and 0x13 (roughly
-corresponds to v1.33 of the game engine, although some of the
+<p>There are two major versions: 0x11 (original one) and 0x13 (roughly<br />
+corresponds to v1.33 of the game engine, although some of the<br />
 features got limited support in v1.3).</p>
 <p>File consists of a sequence of typed sections.</p>
 </p>
@@ -717,7 +717,7 @@ <h3>warcraft_2_pud.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/cpp_stl_11.html b/wav/cpp_stl_11.html
index 92604e38d..59d9c9391 100644
--- a/wav/cpp_stl_11.html
+++ b/wav/cpp_stl_11.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -2147,7 +2147,7 @@ <h3>wav.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/cpp_stl_98.html b/wav/cpp_stl_98.html
index 94043d784..eb156cbe9 100644
--- a/wav/cpp_stl_98.html
+++ b/wav/cpp_stl_98.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -2311,7 +2311,7 @@ <h3>wav.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/csharp.html b/wav/csharp.html
index a40c8d8e5..0ccd0306b 100644
--- a/wav/csharp.html
+++ b/wav/csharp.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1644,7 +1644,7 @@ <h3>Wav.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/go.html b/wav/go.html
index fa8725bfb..f952dfe1d 100644
--- a/wav/go.html
+++ b/wav/go.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1840,7 +1840,7 @@ <h3>wav.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/graphviz.html b/wav/graphviz.html
index 25cc62ab3..582352f6c 100644
--- a/wav/graphviz.html
+++ b/wav/graphviz.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -655,7 +655,7 @@ <h3>wav.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/index.html b/wav/index.html
index bdcbc6bf9..25e006cf2 100644
--- a/wav/index.html
+++ b/wav/index.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -975,7 +975,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/java.html b/wav/java.html
index 624016d8a..d86352afe 100644
--- a/wav/java.html
+++ b/wav/java.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1661,7 +1661,7 @@ <h3>Wav.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/javascript.html b/wav/javascript.html
index e487ee234..0ea4ea473 100644
--- a/wav/javascript.html
+++ b/wav/javascript.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1534,7 +1534,7 @@ <h3>Wav.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/lua.html b/wav/lua.html
index ef56f43be..8531012d0 100644
--- a/wav/lua.html
+++ b/wav/lua.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1188,7 +1188,7 @@ <h3>wav.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/nim.html b/wav/nim.html
index 32934b307..b9aebd088 100644
--- a/wav/nim.html
+++ b/wav/nim.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1394,7 +1394,7 @@ <h3>wav.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/perl.html b/wav/perl.html
index 08e91b2ec..be894d603 100644
--- a/wav/perl.html
+++ b/wav/perl.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1818,7 +1818,7 @@ <h3>Wav.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/php.html b/wav/php.html
index 880534d71..81622c0fd 100644
--- a/wav/php.html
+++ b/wav/php.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1279,7 +1279,7 @@ <h3>Wav.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/python.html b/wav/python.html
index 2b81609b6..1f79a3c86 100644
--- a/wav/python.html
+++ b/wav/python.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1148,7 +1148,7 @@ <h3>wav.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wav/ruby.html b/wav/ruby.html
index e588cb949..165e9fa00 100644
--- a/wav/ruby.html
+++ b/wav/ruby.html
@@ -105,17 +105,17 @@ <h1>Microsoft WAVE audio file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the
-storage of multimedia files. A RIFF file starts out with a file header
-followed by a sequence of data chunks. A WAVE file is often just a RIFF
-file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --
-a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing
+                <p><p>The WAVE file format is a subset of Microsoft's RIFF specification for the<br />
+storage of multimedia files. A RIFF file starts out with a file header<br />
+followed by a sequence of data chunks. A WAVE file is often just a RIFF<br />
+file with a single &quot;WAVE&quot; chunk which consists of two sub-chunks --<br />
+a &quot;fmt &quot; chunk specifying the data format and a &quot;data&quot; chunk containing<br />
 the actual sample data, although other chunks exist and are used.</p>
-<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio
+<p>An extension of the file format is the Broadcast Wave Format (BWF) for radio<br />
 broadcasts. Sample files can be found at:</p>
 <p><a href="https://www.bbc.co.uk/rd/publications/saqas">https://www.bbc.co.uk/rd/publications/saqas</a></p>
-<p>This Kaitai implementation was written by John Byrd of Gigantic Software
-(jbyrd@giganticsoftware.com), and it is likely to contain bugs.</p>
+<p>This Kaitai implementation was written by John Byrd of Gigantic Software<br />
+(<a href="mailto:jbyrd@giganticsoftware.com">jbyrd@giganticsoftware.com</a>), and it is likely to contain bugs.</p>
 </p>
             </div>
             <div class="col-md-4">
@@ -1178,7 +1178,7 @@ <h3>wav.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/cpp_stl_11.html b/websocket/cpp_stl_11.html
index cc07f7414..025eee2bc 100644
--- a/websocket/cpp_stl_11.html
+++ b/websocket/cpp_stl_11.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -736,7 +736,7 @@ <h3>websocket.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/cpp_stl_98.html b/websocket/cpp_stl_98.html
index 505d83caa..eae4eb8ad 100644
--- a/websocket/cpp_stl_98.html
+++ b/websocket/cpp_stl_98.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -777,7 +777,7 @@ <h3>websocket.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/csharp.html b/websocket/csharp.html
index 5dd51ef8d..ff81ca6d3 100644
--- a/websocket/csharp.html
+++ b/websocket/csharp.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -519,7 +519,7 @@ <h3>Websocket.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/go.html b/websocket/go.html
index 10605a050..493fe6bb9 100644
--- a/websocket/go.html
+++ b/websocket/go.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -535,7 +535,7 @@ <h3>websocket.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/graphviz.html b/websocket/graphviz.html
index 2ccbd18c9..3ba9deadb 100644
--- a/websocket/graphviz.html
+++ b/websocket/graphviz.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -343,7 +343,7 @@ <h3>websocket.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/index.html b/websocket/index.html
index 933e8c093..5331936cb 100644
--- a/websocket/index.html
+++ b/websocket/index.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -356,7 +356,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/java.html b/websocket/java.html
index 803c86712..591dbc6da 100644
--- a/websocket/java.html
+++ b/websocket/java.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -548,7 +548,7 @@ <h3>Websocket.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/javascript.html b/websocket/javascript.html
index 856eda4ec..c16e4b704 100644
--- a/websocket/javascript.html
+++ b/websocket/javascript.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -468,7 +468,7 @@ <h3>Websocket.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/lua.html b/websocket/lua.html
index 1298940f4..c5ca3224f 100644
--- a/websocket/lua.html
+++ b/websocket/lua.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -407,7 +407,7 @@ <h3>websocket.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/nim.html b/websocket/nim.html
index 333fb9b70..653475251 100644
--- a/websocket/nim.html
+++ b/websocket/nim.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -436,7 +436,7 @@ <h3>websocket.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/perl.html b/websocket/perl.html
index bf424aef1..769119ba0 100644
--- a/websocket/perl.html
+++ b/websocket/perl.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -549,7 +549,7 @@ <h3>Websocket.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/php.html b/websocket/php.html
index 734639623..74e00b67d 100644
--- a/websocket/php.html
+++ b/websocket/php.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -427,7 +427,7 @@ <h3>Websocket.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/python.html b/websocket/python.html
index 747a5845f..e2e0d13ac 100644
--- a/websocket/python.html
+++ b/websocket/python.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -432,7 +432,7 @@ <h3>websocket.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/websocket/ruby.html b/websocket/ruby.html
index 797440408..f05cd7eea 100644
--- a/websocket/ruby.html
+++ b/websocket/ruby.html
@@ -105,8 +105,8 @@ <h1>WebSocket:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.
-Messages are made up of one or more dataframes, and are delineated by
+                <p><p>The WebSocket protocol establishes a two-way communication channel via TCP.<br />
+Messages are made up of one or more dataframes, and are delineated by<br />
 frames with the <code>fin</code> bit set.</p>
 </p>
             </div>
@@ -447,7 +447,7 @@ <h3>websocket.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/cpp_stl_11.html b/windows_evt_log/cpp_stl_11.html
index 1b4f57c80..daabb6c1f 100644
--- a/windows_evt_log/cpp_stl_11.html
+++ b/windows_evt_log/cpp_stl_11.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -1006,7 +1006,7 @@ <h3>windows_evt_log.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/cpp_stl_98.html b/windows_evt_log/cpp_stl_98.html
index 17c3ebd3e..92a9af1b2 100644
--- a/windows_evt_log/cpp_stl_98.html
+++ b/windows_evt_log/cpp_stl_98.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -1062,7 +1062,7 @@ <h3>windows_evt_log.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/csharp.html b/windows_evt_log/csharp.html
index 8644d0074..2acb61ad7 100644
--- a/windows_evt_log/csharp.html
+++ b/windows_evt_log/csharp.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -819,7 +819,7 @@ <h3>WindowsEvtLog.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/go.html b/windows_evt_log/go.html
index 4164ebf11..55034c527 100644
--- a/windows_evt_log/go.html
+++ b/windows_evt_log/go.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -915,7 +915,7 @@ <h3>windows_evt_log.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/graphviz.html b/windows_evt_log/graphviz.html
index 69aeeb5fb..3347cfa90 100644
--- a/windows_evt_log/graphviz.html
+++ b/windows_evt_log/graphviz.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -417,7 +417,7 @@ <h3>windows_evt_log.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/index.html b/windows_evt_log/index.html
index 611c7784f..ee2e82b47 100644
--- a/windows_evt_log/index.html
+++ b/windows_evt_log/index.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -511,7 +511,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/java.html b/windows_evt_log/java.html
index 0031a64e5..c08ce4fb8 100644
--- a/windows_evt_log/java.html
+++ b/windows_evt_log/java.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -844,7 +844,7 @@ <h3>WindowsEvtLog.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/javascript.html b/windows_evt_log/javascript.html
index bb1812e6c..d81d85744 100644
--- a/windows_evt_log/javascript.html
+++ b/windows_evt_log/javascript.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -677,7 +677,7 @@ <h3>WindowsEvtLog.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/lua.html b/windows_evt_log/lua.html
index fe606dbc7..d8c7bcccc 100644
--- a/windows_evt_log/lua.html
+++ b/windows_evt_log/lua.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -566,7 +566,7 @@ <h3>windows_evt_log.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/nim.html b/windows_evt_log/nim.html
index fae4564b3..9248b8424 100644
--- a/windows_evt_log/nim.html
+++ b/windows_evt_log/nim.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -719,7 +719,7 @@ <h3>windows_evt_log.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/perl.html b/windows_evt_log/perl.html
index 1c593382b..8328cde34 100644
--- a/windows_evt_log/perl.html
+++ b/windows_evt_log/perl.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -791,7 +791,7 @@ <h3>WindowsEvtLog.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/php.html b/windows_evt_log/php.html
index 2919a599e..f6f84c2eb 100644
--- a/windows_evt_log/php.html
+++ b/windows_evt_log/php.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -672,7 +672,7 @@ <h3>WindowsEvtLog.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/python.html b/windows_evt_log/python.html
index 970834c06..fed8efa5b 100644
--- a/windows_evt_log/python.html
+++ b/windows_evt_log/python.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -540,7 +540,7 @@ <h3>windows_evt_log.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_evt_log/ruby.html b/windows_evt_log/ruby.html
index e8df2a7b2..3d169d0b7 100644
--- a/windows_evt_log/ruby.html
+++ b/windows_evt_log/ruby.html
@@ -105,24 +105,24 @@ <h1>Windows Event Log (EVT):
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>EVT files are Windows Event Log files written by older Windows
-operating systems (2000, XP, 2003). They are used as binary log
-files by several major Windows subsystems and
-applications. Typically, several of them can be found in
+                <p><p>EVT files are Windows Event Log files written by older Windows<br />
+operating systems (2000, XP, 2003). They are used as binary log<br />
+files by several major Windows subsystems and<br />
+applications. Typically, several of them can be found in<br />
 <code>%WINDIR%\system32\config</code> directory:</p>
 <ul>
 <li>Application = <code>AppEvent.evt</code></li>
 <li>System = <code>SysEvent.evt</code></li>
 <li>Security = <code>SecEvent.evt</code></li>
 </ul>
-<p>Alternatively, one can export any system event log as distinct .evt
+<p>Alternatively, one can export any system event log as distinct .evt<br />
 file using relevant option in Event Viewer application.</p>
-<p>A Windows application can submit an entry into these logs using
-<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a>
+<p>A Windows application can submit an entry into these logs using<br />
+<a href="https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reporteventa">ReportEventA</a><br />
 function of Windows API.</p>
-<p>Internally, EVT files consist of a fixed-size header and event
-records. There are several usage scenarios (non-wrapping vs wrapping
-log files) which result in slightly different organization of
+<p>Internally, EVT files consist of a fixed-size header and event<br />
+records. There are several usage scenarios (non-wrapping vs wrapping<br />
+log files) which result in slightly different organization of<br />
 records.</p>
 </p>
             </div>
@@ -648,7 +648,7 @@ <h3>windows_evt_log.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/cpp_stl_11.html b/windows_lnk_file/cpp_stl_11.html
index acbf57765..75a482818 100644
--- a/windows_lnk_file/cpp_stl_11.html
+++ b/windows_lnk_file/cpp_stl_11.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -1361,7 +1361,7 @@ <h3>windows_lnk_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/cpp_stl_98.html b/windows_lnk_file/cpp_stl_98.html
index 234ea6ed9..131cbed64 100644
--- a/windows_lnk_file/cpp_stl_98.html
+++ b/windows_lnk_file/cpp_stl_98.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -1489,7 +1489,7 @@ <h3>windows_lnk_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/csharp.html b/windows_lnk_file/csharp.html
index bbc5dde2c..d25c73b3e 100644
--- a/windows_lnk_file/csharp.html
+++ b/windows_lnk_file/csharp.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -940,7 +940,7 @@ <h3>WindowsLnkFile.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/go.html b/windows_lnk_file/go.html
index 9b7b4c7a5..d625490b3 100644
--- a/windows_lnk_file/go.html
+++ b/windows_lnk_file/go.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -1112,7 +1112,7 @@ <h3>windows_lnk_file.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/graphviz.html b/windows_lnk_file/graphviz.html
index 7edc62afb..5fca96a94 100644
--- a/windows_lnk_file/graphviz.html
+++ b/windows_lnk_file/graphviz.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -469,7 +469,7 @@ <h3>windows_lnk_file.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/index.html b/windows_lnk_file/index.html
index 30e982dd8..5631dbe73 100644
--- a/windows_lnk_file/index.html
+++ b/windows_lnk_file/index.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -541,7 +541,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/java.html b/windows_lnk_file/java.html
index 21b9a51dd..b83aed365 100644
--- a/windows_lnk_file/java.html
+++ b/windows_lnk_file/java.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -987,7 +987,7 @@ <h3>WindowsLnkFile.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/javascript.html b/windows_lnk_file/javascript.html
index bc69a14ae..414d1d527 100644
--- a/windows_lnk_file/javascript.html
+++ b/windows_lnk_file/javascript.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -722,7 +722,7 @@ <h3>WindowsLnkFile.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/lua.html b/windows_lnk_file/lua.html
index d001fed8c..ce971b53d 100644
--- a/windows_lnk_file/lua.html
+++ b/windows_lnk_file/lua.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -636,7 +636,7 @@ <h3>windows_lnk_file.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/nim.html b/windows_lnk_file/nim.html
index cef20746a..0890212da 100644
--- a/windows_lnk_file/nim.html
+++ b/windows_lnk_file/nim.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -791,7 +791,7 @@ <h3>windows_lnk_file.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/perl.html b/windows_lnk_file/perl.html
index d7889866c..ba3722b32 100644
--- a/windows_lnk_file/perl.html
+++ b/windows_lnk_file/perl.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -1093,7 +1093,7 @@ <h3>WindowsLnkFile.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/php.html b/windows_lnk_file/php.html
index aa2b7d2a4..b83ed7005 100644
--- a/windows_lnk_file/php.html
+++ b/windows_lnk_file/php.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -726,7 +726,7 @@ <h3>WindowsLnkFile.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/python.html b/windows_lnk_file/python.html
index 0f9e2699a..641a563aa 100644
--- a/windows_lnk_file/python.html
+++ b/windows_lnk_file/python.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -640,7 +640,7 @@ <h3>windows_lnk_file.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_lnk_file/ruby.html b/windows_lnk_file/ruby.html
index 38d692c02..ad071517b 100644
--- a/windows_lnk_file/ruby.html
+++ b/windows_lnk_file/ruby.html
@@ -105,9 +105,9 @@ <h1>Windows shell link file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used
-in Windows shell to create &quot;shortcuts&quot; to another files, usually for
-purposes of running a program from some other directory, sometimes
+                <p><p>Windows .lnk files (AKA &quot;shell link&quot; file) are most frequently used<br />
+in Windows shell to create &quot;shortcuts&quot; to another files, usually for<br />
+purposes of running a program from some other directory, sometimes<br />
 with certain preconfigured arguments and some other options.</p>
 </p>
             </div>
@@ -696,7 +696,7 @@ <h3>windows_lnk_file.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/cpp_stl_11.html b/windows_minidump/cpp_stl_11.html
index 70e64ed86..937a5c34f 100644
--- a/windows_minidump/cpp_stl_11.html
+++ b/windows_minidump/cpp_stl_11.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1344,7 +1344,7 @@ <h3>windows_minidump.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/cpp_stl_98.html b/windows_minidump/cpp_stl_98.html
index 328b03423..3b022cab5 100644
--- a/windows_minidump/cpp_stl_98.html
+++ b/windows_minidump/cpp_stl_98.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1463,7 +1463,7 @@ <h3>windows_minidump.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/csharp.html b/windows_minidump/csharp.html
index 675dcc1da..0afc62b6a 100644
--- a/windows_minidump/csharp.html
+++ b/windows_minidump/csharp.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1028,7 +1028,7 @@ <h3>WindowsMinidump.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/go.html b/windows_minidump/go.html
index 8b0624301..d6ff5e32e 100644
--- a/windows_minidump/go.html
+++ b/windows_minidump/go.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1209,7 +1209,7 @@ <h3>windows_minidump.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/graphviz.html b/windows_minidump/graphviz.html
index 1ceace242..e9643ed1d 100644
--- a/windows_minidump/graphviz.html
+++ b/windows_minidump/graphviz.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -474,7 +474,7 @@ <h3>windows_minidump.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/index.html b/windows_minidump/index.html
index c9537e910..ef4476cbc 100644
--- a/windows_minidump/index.html
+++ b/windows_minidump/index.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -607,7 +607,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/java.html b/windows_minidump/java.html
index c3ed73575..3c5070dac 100644
--- a/windows_minidump/java.html
+++ b/windows_minidump/java.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1080,7 +1080,7 @@ <h3>WindowsMinidump.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/javascript.html b/windows_minidump/javascript.html
index 839eee8f7..1afc43126 100644
--- a/windows_minidump/javascript.html
+++ b/windows_minidump/javascript.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -832,7 +832,7 @@ <h3>WindowsMinidump.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/lua.html b/windows_minidump/lua.html
index 166ac852b..b80ee88b5 100644
--- a/windows_minidump/lua.html
+++ b/windows_minidump/lua.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -691,7 +691,7 @@ <h3>windows_minidump.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/nim.html b/windows_minidump/nim.html
index d27612617..0119a08be 100644
--- a/windows_minidump/nim.html
+++ b/windows_minidump/nim.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -869,7 +869,7 @@ <h3>windows_minidump.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/perl.html b/windows_minidump/perl.html
index 47717054d..5960f3b14 100644
--- a/windows_minidump/perl.html
+++ b/windows_minidump/perl.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -1172,7 +1172,7 @@ <h3>WindowsMinidump.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/php.html b/windows_minidump/php.html
index e13387728..f621c33af 100644
--- a/windows_minidump/php.html
+++ b/windows_minidump/php.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -790,7 +790,7 @@ <h3>WindowsMinidump.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/python.html b/windows_minidump/python.html
index 88f7034d6..27d9c114c 100644
--- a/windows_minidump/python.html
+++ b/windows_minidump/python.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -697,7 +697,7 @@ <h3>windows_minidump.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_minidump/ruby.html b/windows_minidump/ruby.html
index 0649bf8ce..400f3d733 100644
--- a/windows_minidump/ruby.html
+++ b/windows_minidump/ruby.html
@@ -105,12 +105,12 @@ <h1>Windows MiniDump:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process
-core dumps, which is useful for debugging. Given its small size,
-modularity, some cross-platform features and native support in some
-debuggers, it is particularly useful for crash reporting, and is
+                <p><p>Windows MiniDump (MDMP) file provides a concise way to store process<br />
+core dumps, which is useful for debugging. Given its small size,<br />
+modularity, some cross-platform features and native support in some<br />
+debuggers, it is particularly useful for crash reporting, and is<br />
 used for that purpose in Windows and Google Chrome projects.</p>
-<p>The file itself is a container, which contains a number of typed
+<p>The file itself is a container, which contains a number of typed<br />
 &quot;streams&quot;, which contain some data according to its type attribute.</p>
 </p>
             </div>
@@ -754,7 +754,7 @@ <h3>windows_minidump.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/cpp_stl_11.html b/windows_resource_file/cpp_stl_11.html
index a5942c200..2bd535c0f 100644
--- a/windows_resource_file/cpp_stl_11.html
+++ b/windows_resource_file/cpp_stl_11.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -837,7 +837,7 @@ <h3>windows_resource_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/cpp_stl_98.html b/windows_resource_file/cpp_stl_98.html
index 67c579602..c5676c0ae 100644
--- a/windows_resource_file/cpp_stl_98.html
+++ b/windows_resource_file/cpp_stl_98.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -872,7 +872,7 @@ <h3>windows_resource_file.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/csharp.html b/windows_resource_file/csharp.html
index 7a53aa4ca..9cbeccb9d 100644
--- a/windows_resource_file/csharp.html
+++ b/windows_resource_file/csharp.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -654,7 +654,7 @@ <h3>WindowsResourceFile.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/go.html b/windows_resource_file/go.html
index a12299770..76a98a660 100644
--- a/windows_resource_file/go.html
+++ b/windows_resource_file/go.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -719,7 +719,7 @@ <h3>windows_resource_file.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/graphviz.html b/windows_resource_file/graphviz.html
index 7dd9ed953..4de736768 100644
--- a/windows_resource_file/graphviz.html
+++ b/windows_resource_file/graphviz.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -373,7 +373,7 @@ <h3>windows_resource_file.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/index.html b/windows_resource_file/index.html
index 4d41736dd..ab2ddf95b 100644
--- a/windows_resource_file/index.html
+++ b/windows_resource_file/index.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -441,7 +441,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/java.html b/windows_resource_file/java.html
index d2d449241..2feddd08a 100644
--- a/windows_resource_file/java.html
+++ b/windows_resource_file/java.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -650,7 +650,7 @@ <h3>WindowsResourceFile.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/javascript.html b/windows_resource_file/javascript.html
index 724c3edaf..d5834e88c 100644
--- a/windows_resource_file/javascript.html
+++ b/windows_resource_file/javascript.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -585,7 +585,7 @@ <h3>WindowsResourceFile.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/lua.html b/windows_resource_file/lua.html
index b8d5f63f5..3b745c605 100644
--- a/windows_resource_file/lua.html
+++ b/windows_resource_file/lua.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -513,7 +513,7 @@ <h3>windows_resource_file.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/nim.html b/windows_resource_file/nim.html
index 271d0faeb..1e3bb4644 100644
--- a/windows_resource_file/nim.html
+++ b/windows_resource_file/nim.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -566,7 +566,7 @@ <h3>windows_resource_file.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/perl.html b/windows_resource_file/perl.html
index d481c8ff3..6f933e6f2 100644
--- a/windows_resource_file/perl.html
+++ b/windows_resource_file/perl.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -582,7 +582,7 @@ <h3>WindowsResourceFile.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/php.html b/windows_resource_file/php.html
index f9ebca848..25832ef44 100644
--- a/windows_resource_file/php.html
+++ b/windows_resource_file/php.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -538,7 +538,7 @@ <h3>WindowsResourceFile.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/python.html b/windows_resource_file/python.html
index 3a71c5a33..aa317046e 100644
--- a/windows_resource_file/python.html
+++ b/windows_resource_file/python.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -528,7 +528,7 @@ <h3>windows_resource_file.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_resource_file/ruby.html b/windows_resource_file/ruby.html
index 426ed6c14..20ff494ad 100644
--- a/windows_resource_file/ruby.html
+++ b/windows_resource_file/ruby.html
@@ -105,26 +105,26 @@ <h1>Windows resource file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows resource file (.res) are binary bundles of
-&quot;resources&quot;. Resource has some sort of ID (numerical or string),
-type (predefined or user-defined), and raw value. Resource files can
-be seen standalone (as .res file), or embedded inside PE executable
+                <p><p>Windows resource file (.res) are binary bundles of<br />
+&quot;resources&quot;. Resource has some sort of ID (numerical or string),<br />
+type (predefined or user-defined), and raw value. Resource files can<br />
+be seen standalone (as .res file), or embedded inside PE executable<br />
 (.exe, .dll) files.</p>
 <p>Typical use cases include:</p>
 <ul>
 <li>providing information about the application (such as title, copyrights, etc)</li>
 <li>embedding icon(s) to be displayed in file managers into .exe</li>
-<li>adding non-code data into the binary, such as menus, dialog forms,
-cursor images, fonts, various misc bitmaps, and locale-aware
+<li>adding non-code data into the binary, such as menus, dialog forms,<br />
+cursor images, fonts, various misc bitmaps, and locale-aware<br />
 strings</li>
 </ul>
 <p>Windows provides special API to access &quot;resources&quot; from a binary.</p>
-<p>Normally, resources files are created with <code>rc</code> compiler: it takes a
-.rc file (so called &quot;resource-definition script&quot;) + all the raw
-resource binary files for input, and outputs .res file. That .res
+<p>Normally, resources files are created with <code>rc</code> compiler: it takes a<br />
+.rc file (so called &quot;resource-definition script&quot;) + all the raw<br />
+resource binary files for input, and outputs .res file. That .res<br />
 file can be linked into an .exe / .dll afterwards using a linker.</p>
-<p>Internally, resource file is just a sequence of individual resource
-definitions. RC tool ensures that first resource (#0) is always
+<p>Internally, resource file is just a sequence of individual resource<br />
+definitions. RC tool ensures that first resource (#0) is always<br />
 empty.</p>
 </p>
             </div>
@@ -545,7 +545,7 @@ <h3>windows_resource_file.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/cpp_stl_11.html b/windows_shell_items/cpp_stl_11.html
index 2ba3d9f4c..d997f094f 100644
--- a/windows_shell_items/cpp_stl_11.html
+++ b/windows_shell_items/cpp_stl_11.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -800,7 +800,7 @@ <h3>windows_shell_items.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/cpp_stl_98.html b/windows_shell_items/cpp_stl_98.html
index 521401956..0bd753a8c 100644
--- a/windows_shell_items/cpp_stl_98.html
+++ b/windows_shell_items/cpp_stl_98.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -856,7 +856,7 @@ <h3>windows_shell_items.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/csharp.html b/windows_shell_items/csharp.html
index 87967d950..2592e4c18 100644
--- a/windows_shell_items/csharp.html
+++ b/windows_shell_items/csharp.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h3>WindowsShellItems.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/go.html b/windows_shell_items/go.html
index a8d07f587..e13ca49f8 100644
--- a/windows_shell_items/go.html
+++ b/windows_shell_items/go.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -556,7 +556,7 @@ <h3>windows_shell_items.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/graphviz.html b/windows_shell_items/graphviz.html
index 5e007611a..252547e1f 100644
--- a/windows_shell_items/graphviz.html
+++ b/windows_shell_items/graphviz.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -376,7 +376,7 @@ <h3>windows_shell_items.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/index.html b/windows_shell_items/index.html
index e3afb2713..7ac851e18 100644
--- a/windows_shell_items/index.html
+++ b/windows_shell_items/index.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -348,7 +348,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/java.html b/windows_shell_items/java.html
index 557a04357..958291f08 100644
--- a/windows_shell_items/java.html
+++ b/windows_shell_items/java.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -607,7 +607,7 @@ <h3>WindowsShellItems.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/javascript.html b/windows_shell_items/javascript.html
index 1061bf386..49ecf980f 100644
--- a/windows_shell_items/javascript.html
+++ b/windows_shell_items/javascript.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -500,7 +500,7 @@ <h3>WindowsShellItems.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/lua.html b/windows_shell_items/lua.html
index 4286c1f6f..1d9306e7d 100644
--- a/windows_shell_items/lua.html
+++ b/windows_shell_items/lua.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -441,7 +441,7 @@ <h3>windows_shell_items.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/nim.html b/windows_shell_items/nim.html
index fbf7e2fb3..dea56f79a 100644
--- a/windows_shell_items/nim.html
+++ b/windows_shell_items/nim.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -493,7 +493,7 @@ <h3>windows_shell_items.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/perl.html b/windows_shell_items/perl.html
index 286d7eab5..bf7ee4a85 100644
--- a/windows_shell_items/perl.html
+++ b/windows_shell_items/perl.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -593,7 +593,7 @@ <h3>WindowsShellItems.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/php.html b/windows_shell_items/php.html
index b14cb3df5..6a578d142 100644
--- a/windows_shell_items/php.html
+++ b/windows_shell_items/php.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -444,7 +444,7 @@ <h3>WindowsShellItems.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/python.html b/windows_shell_items/python.html
index fe99940c0..47203500c 100644
--- a/windows_shell_items/python.html
+++ b/windows_shell_items/python.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -467,7 +467,7 @@ <h3>windows_shell_items.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_shell_items/ruby.html b/windows_shell_items/ruby.html
index 67eeddcc5..ae7274ddd 100644
--- a/windows_shell_items/ruby.html
+++ b/windows_shell_items/ruby.html
@@ -105,16 +105,16 @@ <h1>Windows Shell Items:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of
-structures used internally within Windows to identify paths in
-Windows Folder Hierarchy. It is widely used in Windows Shell (and
-most visible in File Explorer), both as in-memory and in-file
+                <p><p>Windows Shell Items (AKA &quot;shellbags&quot;) is an undocumented set of<br />
+structures used internally within Windows to identify paths in<br />
+Windows Folder Hierarchy. It is widely used in Windows Shell (and<br />
+most visible in File Explorer), both as in-memory and in-file<br />
 structures. Some formats embed them, namely:</p>
 <ul>
 <li>Windows Shell link files (.lnk) Windows registry</li>
 <li>Windows registry &quot;ShellBags&quot; keys</li>
 </ul>
-<p>The format is mostly undocumented, and is known to vary between
+<p>The format is mostly undocumented, and is known to vary between<br />
 various Windows versions.</p>
 </p>
             </div>
@@ -474,7 +474,7 @@ <h3>windows_shell_items.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/cpp_stl_11.html b/windows_systemtime/cpp_stl_11.html
index 3842adfc3..963da460b 100644
--- a/windows_systemtime/cpp_stl_11.html
+++ b/windows_systemtime/cpp_stl_11.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -480,7 +480,7 @@ <h3>windows_systemtime.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/cpp_stl_98.html b/windows_systemtime/cpp_stl_98.html
index 433142f47..c6a4ba4df 100644
--- a/windows_systemtime/cpp_stl_98.html
+++ b/windows_systemtime/cpp_stl_98.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -488,7 +488,7 @@ <h3>windows_systemtime.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/csharp.html b/windows_systemtime/csharp.html
index 4a8178d98..ab3f33ed0 100644
--- a/windows_systemtime/csharp.html
+++ b/windows_systemtime/csharp.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -405,7 +405,7 @@ <h3>WindowsSystemtime.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/go.html b/windows_systemtime/go.html
index 3dbeab33b..8eb07a89e 100644
--- a/windows_systemtime/go.html
+++ b/windows_systemtime/go.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -378,7 +378,7 @@ <h3>windows_systemtime.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/graphviz.html b/windows_systemtime/graphviz.html
index 86c43a427..307e82a1e 100644
--- a/windows_systemtime/graphviz.html
+++ b/windows_systemtime/graphviz.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -291,7 +291,7 @@ <h3>windows_systemtime.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/index.html b/windows_systemtime/index.html
index 6bf6b96ac..6f19102ea 100644
--- a/windows_systemtime/index.html
+++ b/windows_systemtime/index.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -302,7 +302,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/java.html b/windows_systemtime/java.html
index 5fd694d95..119cddb5e 100644
--- a/windows_systemtime/java.html
+++ b/windows_systemtime/java.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -410,7 +410,7 @@ <h3>WindowsSystemtime.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/javascript.html b/windows_systemtime/javascript.html
index 84c0426b7..9df7b173c 100644
--- a/windows_systemtime/javascript.html
+++ b/windows_systemtime/javascript.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -382,7 +382,7 @@ <h3>WindowsSystemtime.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/lua.html b/windows_systemtime/lua.html
index e2ec8ac31..b37742345 100644
--- a/windows_systemtime/lua.html
+++ b/windows_systemtime/lua.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -318,7 +318,7 @@ <h3>windows_systemtime.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/nim.html b/windows_systemtime/nim.html
index 98d3c7675..634ce8a94 100644
--- a/windows_systemtime/nim.html
+++ b/windows_systemtime/nim.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -355,7 +355,7 @@ <h3>windows_systemtime.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/perl.html b/windows_systemtime/perl.html
index 6ba65021e..1ac00c805 100644
--- a/windows_systemtime/perl.html
+++ b/windows_systemtime/perl.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -358,7 +358,7 @@ <h3>WindowsSystemtime.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/php.html b/windows_systemtime/php.html
index 749a05560..b4110e373 100644
--- a/windows_systemtime/php.html
+++ b/windows_systemtime/php.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -346,7 +346,7 @@ <h3>WindowsSystemtime.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/python.html b/windows_systemtime/python.html
index 9e7de7c01..01ccfaac3 100644
--- a/windows_systemtime/python.html
+++ b/windows_systemtime/python.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -346,7 +346,7 @@ <h3>windows_systemtime.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/windows_systemtime/ruby.html b/windows_systemtime/ruby.html
index 69628814b..49ecba237 100644
--- a/windows_systemtime/ruby.html
+++ b/windows_systemtime/ruby.html
@@ -105,7 +105,7 @@ <h1>Microsoft Windows SYSTEMTIME structure:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components
+                <p><p>Microsoft Windows SYSTEMTIME structure, stores individual components<br />
 of date and time as individual fields, up to millisecond precision.</p>
 </p>
             </div>
@@ -376,7 +376,7 @@ <h3>windows_systemtime.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/cpp_stl_11.html b/wmf/cpp_stl_11.html
index bd25207d4..72dbff882 100644
--- a/wmf/cpp_stl_11.html
+++ b/wmf/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1312,7 +1312,7 @@ <h3>wmf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/cpp_stl_98.html b/wmf/cpp_stl_98.html
index 8bcdb18dc..58e1831d1 100644
--- a/wmf/cpp_stl_98.html
+++ b/wmf/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1422,7 +1422,7 @@ <h3>wmf.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/csharp.html b/wmf/csharp.html
index e0603de0d..ebe6f135b 100644
--- a/wmf/csharp.html
+++ b/wmf/csharp.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1002,7 +1002,7 @@ <h3>Wmf.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/go.html b/wmf/go.html
index 933fb6cf3..d4d823c7c 100644
--- a/wmf/go.html
+++ b/wmf/go.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1085,7 +1085,7 @@ <h3>wmf.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/graphviz.html b/wmf/graphviz.html
index ab60f2d61..a5bae3a1e 100644
--- a/wmf/graphviz.html
+++ b/wmf/graphviz.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -461,7 +461,7 @@ <h3>wmf.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/index.html b/wmf/index.html
index 5e44db9ba..9ac1ab086 100644
--- a/wmf/index.html
+++ b/wmf/index.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -544,7 +544,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/java.html b/wmf/java.html
index 3c14d4144..38e8279ae 100644
--- a/wmf/java.html
+++ b/wmf/java.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1118,7 +1118,7 @@ <h3>Wmf.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/javascript.html b/wmf/javascript.html
index b9be6f9fa..b304fab97 100644
--- a/wmf/javascript.html
+++ b/wmf/javascript.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -906,7 +906,7 @@ <h3>Wmf.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/lua.html b/wmf/lua.html
index 489a1e76d..7df08baff 100644
--- a/wmf/lua.html
+++ b/wmf/lua.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -708,7 +708,7 @@ <h3>wmf.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/nim.html b/wmf/nim.html
index 3d8169583..f791c58bc 100644
--- a/wmf/nim.html
+++ b/wmf/nim.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -841,7 +841,7 @@ <h3>wmf.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/perl.html b/wmf/perl.html
index f1ca833b6..5bc454b8a 100644
--- a/wmf/perl.html
+++ b/wmf/perl.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -1096,7 +1096,7 @@ <h3>Wmf.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/php.html b/wmf/php.html
index ef2cb9304..dafb0e59c 100644
--- a/wmf/php.html
+++ b/wmf/php.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -789,7 +789,7 @@ <h3>Wmf.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/python.html b/wmf/python.html
index d201e572b..2c2996051 100644
--- a/wmf/python.html
+++ b/wmf/python.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -704,7 +704,7 @@ <h3>wmf.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/wmf/ruby.html b/wmf/ruby.html
index 460259c15..4a8df66c2 100644
--- a/wmf/ruby.html
+++ b/wmf/ruby.html
@@ -105,11 +105,11 @@ <h1>Windows Metafile (WMF) vector image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>WMF (Windows Metafile) is a relatively early vector image format
+                <p><p>WMF (Windows Metafile) is a relatively early vector image format<br />
 introduced for Microsoft Windows in 1990.</p>
-<p>Inside, it provides a serialized list of Windows GDI (Graphics
-Device Interface) function calls, which, if played back, result in
-an image being drawn on a given surface (display, off-screen buffer,
+<p>Inside, it provides a serialized list of Windows GDI (Graphics<br />
+Device Interface) function calls, which, if played back, result in<br />
+an image being drawn on a given surface (display, off-screen buffer,<br />
 printer, etc).</p>
 </p>
             </div>
@@ -767,7 +767,7 @@ <h3>wmf.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/cpp_stl_11.html b/xar/cpp_stl_11.html
index 558f0885f..fb285ce10 100644
--- a/xar/cpp_stl_11.html
+++ b/xar/cpp_stl_11.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -741,7 +741,7 @@ <h3>xar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/cpp_stl_98.html b/xar/cpp_stl_98.html
index b146ecdd6..e16f88f88 100644
--- a/xar/cpp_stl_98.html
+++ b/xar/cpp_stl_98.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -782,7 +782,7 @@ <h3>xar.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/csharp.html b/xar/csharp.html
index ee801580e..78e037351 100644
--- a/xar/csharp.html
+++ b/xar/csharp.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h3>Xar.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/go.html b/xar/go.html
index 32d55af56..bcb44e6ca 100644
--- a/xar/go.html
+++ b/xar/go.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -619,7 +619,7 @@ <h3>xar.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/index.html b/xar/index.html
index e1695f81c..395e977d8 100644
--- a/xar/index.html
+++ b/xar/index.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -377,7 +377,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/java.html b/xar/java.html
index 7269eb50b..4d302a21c 100644
--- a/xar/java.html
+++ b/xar/java.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -593,7 +593,7 @@ <h3>Xar.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/javascript.html b/xar/javascript.html
index 816efa027..95df4f189 100644
--- a/xar/javascript.html
+++ b/xar/javascript.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -508,7 +508,7 @@ <h3>Xar.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/lua.html b/xar/lua.html
index a89993c26..03681fa66 100644
--- a/xar/lua.html
+++ b/xar/lua.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -448,7 +448,7 @@ <h3>xar.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/php.html b/xar/php.html
index 591877876..bf3269360 100644
--- a/xar/php.html
+++ b/xar/php.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -466,7 +466,7 @@ <h3>Xar.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/python.html b/xar/python.html
index a1b23ad24..5141a2199 100644
--- a/xar/python.html
+++ b/xar/python.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -462,7 +462,7 @@ <h3>xar.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xar/ruby.html b/xar/ruby.html
index 065eaab49..f40c18722 100644
--- a/xar/ruby.html
+++ b/xar/ruby.html
@@ -106,9 +106,9 @@ <h1>XAR (eXtensible ARchive):
         <div class="row">
             <div class="col-md-8">
                 <p><p>From <a href="https://en.wikipedia.org/wiki/Xar_(archiver)">Wikipedia</a>:</p>
-<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver
-and the archiver's file format. It was created within the OpenDarwin project
-and is used in macOS X 10.5 and up for software installation routines, as
+<p>&quot;XAR (short for eXtensible ARchive format) is an open source file archiver<br />
+and the archiver's file format. It was created within the OpenDarwin project<br />
+and is used in macOS X 10.5 and up for software installation routines, as<br />
 well as browser extensions in Safari 5.0 and up.&quot;</p>
 </p>
             </div>
@@ -475,7 +475,7 @@ <h3>xar.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xref.html b/xref.html
index dd1411498..b796bd6c2 100644
--- a/xref.html
+++ b/xref.html
@@ -4007,7 +4007,7 @@ <h1>Cross-References</h1>
                 <td>CC0-1.0</td>
 
                 <td></td>
-                <td><a href="https://tools.ietf.org/html/rfc793">793</a>, <a href="https://tools.ietf.org/html/rfc1323">1323</a></td>
+                <td><a href="https://tools.ietf.org/html/rfc793">793</a>, <a href="https://tools.ietf.org/html/rfc1323">1323</a>, <a href="https://tools.ietf.org/html/rfc9293">9293</a></td>
                 <!--
                 <td></td>
                 <td></td>
@@ -4782,7 +4782,7 @@ <h1>Cross-References</h1>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/cpp_stl_11.html b/xwd/cpp_stl_11.html
index d5467c629..6b6c659fe 100644
--- a/xwd/cpp_stl_11.html
+++ b/xwd/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -783,7 +783,7 @@ <h3>xwd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/cpp_stl_98.html b/xwd/cpp_stl_98.html
index 4adcb6e65..cceedc96c 100644
--- a/xwd/cpp_stl_98.html
+++ b/xwd/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -824,7 +824,7 @@ <h3>xwd.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/csharp.html b/xwd/csharp.html
index b65b0b62a..4fe1b85f2 100644
--- a/xwd/csharp.html
+++ b/xwd/csharp.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -661,7 +661,7 @@ <h3>Xwd.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/go.html b/xwd/go.html
index 80c2abc8a..e78782f36 100644
--- a/xwd/go.html
+++ b/xwd/go.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>xwd.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/graphviz.html b/xwd/graphviz.html
index 11af4977e..979f81360 100644
--- a/xwd/graphviz.html
+++ b/xwd/graphviz.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -358,7 +358,7 @@ <h3>xwd.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/index.html b/xwd/index.html
index 517c4fb00..25f910866 100644
--- a/xwd/index.html
+++ b/xwd/index.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -422,7 +422,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/java.html b/xwd/java.html
index ae3451eb9..82aaa62ae 100644
--- a/xwd/java.html
+++ b/xwd/java.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -708,7 +708,7 @@ <h3>Xwd.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/javascript.html b/xwd/javascript.html
index b8857f4dc..0316d7304 100644
--- a/xwd/javascript.html
+++ b/xwd/javascript.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -580,7 +580,7 @@ <h3>Xwd.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/lua.html b/xwd/lua.html
index 2c9b97a5e..52bfddd54 100644
--- a/xwd/lua.html
+++ b/xwd/lua.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -465,7 +465,7 @@ <h3>xwd.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/nim.html b/xwd/nim.html
index b387e4841..1922e1918 100644
--- a/xwd/nim.html
+++ b/xwd/nim.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -588,7 +588,7 @@ <h3>xwd.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/perl.html b/xwd/perl.html
index a976f89e2..15f1a9107 100644
--- a/xwd/perl.html
+++ b/xwd/perl.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -632,7 +632,7 @@ <h3>Xwd.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/php.html b/xwd/php.html
index 82b8977cc..50cfa8f15 100644
--- a/xwd/php.html
+++ b/xwd/php.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -590,7 +590,7 @@ <h3>Xwd.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/python.html b/xwd/python.html
index 2683bdc9d..87d4b185f 100644
--- a/xwd/python.html
+++ b/xwd/python.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -441,7 +441,7 @@ <h3>xwd.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/xwd/ruby.html b/xwd/ruby.html
index 15bef3aa1..ae6f69802 100644
--- a/xwd/ruby.html
+++ b/xwd/ruby.html
@@ -105,13 +105,13 @@ <h1>xwd (X Window Dump) bitmap image:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>xwd is a file format written by eponymous X11 screen capture
-application (xwd stands for &quot;X Window Dump&quot;). Typically, an average
-user transforms xwd format into something more widespread by any of
+                <p><p>xwd is a file format written by eponymous X11 screen capture<br />
+application (xwd stands for &quot;X Window Dump&quot;). Typically, an average<br />
+user transforms xwd format into something more widespread by any of<br />
 <code>xwdtopnm</code> and <code>pnmto...</code> utilities right away.</p>
-<p>xwd format itself provides a raw uncompressed bitmap with some
-metainformation, like pixel format, width, height, bit depth,
-etc. Note that technically format includes machine-dependent fields
+<p>xwd format itself provides a raw uncompressed bitmap with some<br />
+metainformation, like pixel format, width, height, bit depth,<br />
+etc. Note that technically format includes machine-dependent fields<br />
 and thus is probably a poor choice for true cross-platform usage.</p>
 </p>
             </div>
@@ -564,7 +564,7 @@ <h3>xwd.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/cpp_stl_11.html b/zip/cpp_stl_11.html
index 90b164509..1ef7eaf34 100644
--- a/zip/cpp_stl_11.html
+++ b/zip/cpp_stl_11.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1743,7 +1743,7 @@ <h3>zip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/cpp_stl_98.html b/zip/cpp_stl_98.html
index 5f31b3cb7..ec36b23d9 100644
--- a/zip/cpp_stl_98.html
+++ b/zip/cpp_stl_98.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1916,7 +1916,7 @@ <h3>zip.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/csharp.html b/zip/csharp.html
index 0174c98fe..016203012 100644
--- a/zip/csharp.html
+++ b/zip/csharp.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1258,7 +1258,7 @@ <h3>Zip.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/go.html b/zip/go.html
index 6d3759a6d..1247836d5 100644
--- a/zip/go.html
+++ b/zip/go.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1483,7 +1483,7 @@ <h3>zip.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/graphviz.html b/zip/graphviz.html
index fab1a02eb..517a4bee8 100644
--- a/zip/graphviz.html
+++ b/zip/graphviz.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -584,7 +584,7 @@ <h3>zip.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/index.html b/zip/index.html
index dcb27ecd9..49881c3d6 100644
--- a/zip/index.html
+++ b/zip/index.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -649,7 +649,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/java.html b/zip/java.html
index 6582dd5f2..f1e8fe244 100644
--- a/zip/java.html
+++ b/zip/java.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1340,7 +1340,7 @@ <h3>Zip.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/javascript.html b/zip/javascript.html
index 46880fdb5..d8dfe9b68 100644
--- a/zip/javascript.html
+++ b/zip/javascript.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -966,7 +966,7 @@ <h3>Zip.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/lua.html b/zip/lua.html
index b2b70b7c4..1c2484463 100644
--- a/zip/lua.html
+++ b/zip/lua.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -823,7 +823,7 @@ <h3>zip.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/nim.html b/zip/nim.html
index 2a4b0bf44..df0e9ea52 100644
--- a/zip/nim.html
+++ b/zip/nim.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1061,7 +1061,7 @@ <h3>zip.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/perl.html b/zip/perl.html
index b9562795d..5dffff0f7 100644
--- a/zip/perl.html
+++ b/zip/perl.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -1509,7 +1509,7 @@ <h3>Zip.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/php.html b/zip/php.html
index 08c44ef91..6db68e3cc 100644
--- a/zip/php.html
+++ b/zip/php.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -989,7 +989,7 @@ <h3>Zip.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/python.html b/zip/python.html
index 38bf5228e..d4841b5b2 100644
--- a/zip/python.html
+++ b/zip/python.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -799,7 +799,7 @@ <h3>zip.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zip/ruby.html b/zip/ruby.html
index 21fc44880..98dbbb639 100644
--- a/zip/ruby.html
+++ b/zip/ruby.html
@@ -105,13 +105,13 @@ <h1>ZIP archive file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz
+                <p><p>ZIP is a popular archive file format, introduced in 1989 by Phil Katz<br />
 and originally implemented in PKZIP utility by PKWARE.</p>
-<p>Thanks to solid support of it in most desktop environments and
-operating systems, and algorithms / specs availability in public
-domain, it quickly became tool of choice for implementing file
+<p>Thanks to solid support of it in most desktop environments and<br />
+operating systems, and algorithms / specs availability in public<br />
+domain, it quickly became tool of choice for implementing file<br />
 containers.</p>
-<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files
+<p>For example, Java .jar files, OpenDocument, Office Open XML, EPUB files<br />
 are actually ZIP archives.</p>
 </p>
             </div>
@@ -897,7 +897,7 @@ <h3>zip.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/cpp_stl_11.html b/zisofs/cpp_stl_11.html
index b5912dfcb..037a6cbdc 100644
--- a/zisofs/cpp_stl_11.html
+++ b/zisofs/cpp_stl_11.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -682,7 +682,7 @@ <h3>zisofs.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/cpp_stl_98.html b/zisofs/cpp_stl_98.html
index f47a99b31..1e74d0e50 100644
--- a/zisofs/cpp_stl_98.html
+++ b/zisofs/cpp_stl_98.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -717,7 +717,7 @@ <h3>zisofs.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/csharp.html b/zisofs/csharp.html
index 760b5dff4..6380ed986 100644
--- a/zisofs/csharp.html
+++ b/zisofs/csharp.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -548,7 +548,7 @@ <h3>Zisofs.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/go.html b/zisofs/go.html
index 89c027699..1c2fb9e7e 100644
--- a/zisofs/go.html
+++ b/zisofs/go.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -552,7 +552,7 @@ <h3>zisofs.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/graphviz.html b/zisofs/graphviz.html
index c306491ae..0fb574e1b 100644
--- a/zisofs/graphviz.html
+++ b/zisofs/graphviz.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -348,7 +348,7 @@ <h3>zisofs.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/index.html b/zisofs/index.html
index 7819e8716..6841e2139 100644
--- a/zisofs/index.html
+++ b/zisofs/index.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -342,7 +342,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/java.html b/zisofs/java.html
index 6d2525337..63feb1c22 100644
--- a/zisofs/java.html
+++ b/zisofs/java.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -529,7 +529,7 @@ <h3>Zisofs.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/javascript.html b/zisofs/javascript.html
index 207e5e28d..518aad7e5 100644
--- a/zisofs/javascript.html
+++ b/zisofs/javascript.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -476,7 +476,7 @@ <h3>Zisofs.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/lua.html b/zisofs/lua.html
index 62f07d904..292edbf9c 100644
--- a/zisofs/lua.html
+++ b/zisofs/lua.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -428,7 +428,7 @@ <h3>zisofs.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/nim.html b/zisofs/nim.html
index b221cc352..c1bcd9a35 100644
--- a/zisofs/nim.html
+++ b/zisofs/nim.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -454,7 +454,7 @@ <h3>zisofs.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/perl.html b/zisofs/perl.html
index 2bbe7bcfb..e08cb40ff 100644
--- a/zisofs/perl.html
+++ b/zisofs/perl.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -487,7 +487,7 @@ <h3>Zisofs.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/php.html b/zisofs/php.html
index 6fb9d65bf..ed5986e0a 100644
--- a/zisofs/php.html
+++ b/zisofs/php.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -436,7 +436,7 @@ <h3>Zisofs.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/python.html b/zisofs/python.html
index c86a83563..4d566c413 100644
--- a/zisofs/python.html
+++ b/zisofs/python.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -445,7 +445,7 @@ <h3>zisofs.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zisofs/ruby.html b/zisofs/ruby.html
index d36764e60..ee22e1231 100644
--- a/zisofs/ruby.html
+++ b/zisofs/ruby.html
@@ -105,14 +105,14 @@ <h1>zisofs:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>zisofs is a compression format for files on ISO9660 file system. It has
-limited support across operating systems, mainly Linux kernel. Typically a
-directory tree is first preprocessed by mkzftree (from the zisofs-tools
-package before being turned into an ISO9660 image by mkisofs, genisoimage
+                <p><p>zisofs is a compression format for files on ISO9660 file system. It has<br />
+limited support across operating systems, mainly Linux kernel. Typically a<br />
+directory tree is first preprocessed by mkzftree (from the zisofs-tools<br />
+package before being turned into an ISO9660 image by mkisofs, genisoimage<br />
 or similar tool. The data is zlib compressed.</p>
-<p>The specification here describes the structure of a file that has been
-preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not
-decompressed, as blocks with length 0 have a special meaning. Decompression
+<p>The specification here describes the structure of a file that has been<br />
+preprocessed by mkzftree, not of a full ISO9660 ziso. Data is not<br />
+decompressed, as blocks with length 0 have a special meaning. Decompression<br />
 and deconstruction of this data should be done outside of Kaitai Struct.</p>
 </p>
             </div>
@@ -445,7 +445,7 @@ <h3>zisofs.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/cpp_stl_11.html b/zx_spectrum_tap/cpp_stl_11.html
index 1d00ae6b9..8745cab46 100644
--- a/zx_spectrum_tap/cpp_stl_11.html
+++ b/zx_spectrum_tap/cpp_stl_11.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -788,7 +788,7 @@ <h3>zx_spectrum_tap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/cpp_stl_98.html b/zx_spectrum_tap/cpp_stl_98.html
index 03fd2bd6e..d3afd1939 100644
--- a/zx_spectrum_tap/cpp_stl_98.html
+++ b/zx_spectrum_tap/cpp_stl_98.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -838,7 +838,7 @@ <h3>zx_spectrum_tap.cpp</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/csharp.html b/zx_spectrum_tap/csharp.html
index 4313b587d..bb8e8b96e 100644
--- a/zx_spectrum_tap/csharp.html
+++ b/zx_spectrum_tap/csharp.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -579,7 +579,7 @@ <h3>ZxSpectrumTap.cs</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/go.html b/zx_spectrum_tap/go.html
index bd85e438e..ce0571eb9 100644
--- a/zx_spectrum_tap/go.html
+++ b/zx_spectrum_tap/go.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -581,7 +581,7 @@ <h3>zx_spectrum_tap.go</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/graphviz.html b/zx_spectrum_tap/graphviz.html
index 28fa36f0b..bd77f21d6 100644
--- a/zx_spectrum_tap/graphviz.html
+++ b/zx_spectrum_tap/graphviz.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -370,7 +370,7 @@ <h3>zx_spectrum_tap.dot</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/index.html b/zx_spectrum_tap/index.html
index 5b1776a4b..eea9b51f6 100644
--- a/zx_spectrum_tap/index.html
+++ b/zx_spectrum_tap/index.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -359,7 +359,7 @@ <h2>Format specification in Kaitai Struct YAML</h2>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/java.html b/zx_spectrum_tap/java.html
index c9dcce43b..022de6500 100644
--- a/zx_spectrum_tap/java.html
+++ b/zx_spectrum_tap/java.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -635,7 +635,7 @@ <h3>ZxSpectrumTap.java</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/javascript.html b/zx_spectrum_tap/javascript.html
index e1b3d3c37..014c997a0 100644
--- a/zx_spectrum_tap/javascript.html
+++ b/zx_spectrum_tap/javascript.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -500,7 +500,7 @@ <h3>ZxSpectrumTap.js</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/lua.html b/zx_spectrum_tap/lua.html
index cf429f822..f4060e69b 100644
--- a/zx_spectrum_tap/lua.html
+++ b/zx_spectrum_tap/lua.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -432,7 +432,7 @@ <h3>zx_spectrum_tap.lua</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/nim.html b/zx_spectrum_tap/nim.html
index 9722d300c..e04c33fd7 100644
--- a/zx_spectrum_tap/nim.html
+++ b/zx_spectrum_tap/nim.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -478,7 +478,7 @@ <h3>zx_spectrum_tap.nim</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/perl.html b/zx_spectrum_tap/perl.html
index 8e2dae6f1..f3a69e4fd 100644
--- a/zx_spectrum_tap/perl.html
+++ b/zx_spectrum_tap/perl.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -618,7 +618,7 @@ <h3>ZxSpectrumTap.pm</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/php.html b/zx_spectrum_tap/php.html
index 7fe7d3838..d499cddfa 100644
--- a/zx_spectrum_tap/php.html
+++ b/zx_spectrum_tap/php.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -470,7 +470,7 @@ <h3>ZxSpectrumTap.php</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/python.html b/zx_spectrum_tap/python.html
index 326ff7a70..f1de567a2 100644
--- a/zx_spectrum_tap/python.html
+++ b/zx_spectrum_tap/python.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -452,7 +452,7 @@ <h3>zx_spectrum_tap.py</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>
 
diff --git a/zx_spectrum_tap/ruby.html b/zx_spectrum_tap/ruby.html
index f70f87955..b361e32a2 100644
--- a/zx_spectrum_tap/ruby.html
+++ b/zx_spectrum_tap/ruby.html
@@ -105,11 +105,11 @@ <h1>ZX Spectrum tape file:
 
         <div class="row">
             <div class="col-md-8">
-                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in
-1982 by Sinclair Research). TAP file stores blocks of data as if
-they are written to magnetic tape, which was used as primary media
-for ZX Spectrum. Contents of this file can be viewed as a very
-simple linear filesystem, storing named files with some basic
+                <p><p>TAP files are used by emulators of ZX Spectrum computer (released in<br />
+1982 by Sinclair Research). TAP file stores blocks of data as if<br />
+they are written to magnetic tape, which was used as primary media<br />
+for ZX Spectrum. Contents of this file can be viewed as a very<br />
+simple linear filesystem, storing named files with some basic<br />
 metainformation prepended as a header.</p>
 </p>
             </div>
@@ -478,7 +478,7 @@ <h3>zx_spectrum_tap.rb</h3>
 
     <footer id="main-footer">
         <div class="container">
-            &copy; 2015&ndash;2023 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
+            &copy; 2015&ndash;2024 Kaitai Project and <a href="https://github.com/kaitai-io/kaitai_struct_formats/graphs/contributors">format repo contributors</a>
 
             <h3>Contacts</h3>