Hi,

following patch fixes some more W3C validation issues inside the release
notes

[[[
Make the release notes more compliant with the XHTML 1.1 standard.

* docs/release-notes/1.6.html
  (Testsuite fails): add missing closing p-tag

* docs/release-notes/1.7.html
  (svn diff can show git-style diff annotations): close p-tag before ul

* docs/release-notes/1.8.html
  (Skelta style updates are now the default): drop invalid p-section

* docs/release-notes/1.9.html
  (fsvnadmin pack): correct typo (missing / for closing tag)
  (svnadmin setrevprop --transaction): fix incorrect closing tag
]]]

Regards,
Stefan

Index: docs/release-notes/1.6.html
===================================================================
--- docs/release-notes/1.6.html	(revision 1743727)
+++ docs/release-notes/1.6.html	(working copy)
@@ -956,18 +956,19 @@
 </h3>
 
 <p>There are known testsuite fails that occur intermittently:
-  <ul>
-    <li>log_tests.py 30. This can be fixed by patching
-    with <a href="http://svn.apache.org/r1293229";>r1293229</a> from
-    trunk.
-    </li>
-    <li>diff_tests.py 32 as the testsuite does not account for the
-    random output order of 'svn diff'.
-    </li>
-    <li>Ruby swig test_dump as the testsuite does not account for the
-    random property order in dump files.
-    </li>
-  </ul>
+</p>
+<ul>
+  <li>log_tests.py 30. This can be fixed by patching
+  with <a href="http://svn.apache.org/r1293229";>r1293229</a> from
+  trunk.
+  </li>
+  <li>diff_tests.py 32 as the testsuite does not account for the
+  random output order of 'svn diff'.
+  </li>
+  <li>Ruby swig test_dump as the testsuite does not account for the
+  random property order in dump files.
+  </li>
+</ul>
 
 </div>  <!-- test-fail-issue -->
 
Index: docs/release-notes/1.7.html
===================================================================
--- docs/release-notes/1.7.html	(revision 1743727)
+++ docs/release-notes/1.7.html	(working copy)
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" 
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" 
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
 <html xmlns="http://www.w3.org/1999/xhtml";>
 <head>
@@ -866,6 +866,7 @@
 <a href="http://www.kernel.org/pub/software/scm/git/docs/git-apply.html";
 >git-apply</a>, but there are limitations due to differences between
 Subversion and git:
+</p>
 <ul>
   <li><tt>svn diff</tt> currently cannot display rename information.
       Renames are always shown as a copy and a delete.</li>
@@ -877,7 +878,6 @@
       This may prevent git-apply from applying such patches without
       modification.</li>
 </ul>
-</p>
 
 <p>In a future release of Subversion,
 <a href="#patch"><tt>svn patch</tt></a> will receive support for the
Index: docs/release-notes/1.8.html
===================================================================
--- docs/release-notes/1.8.html	(revision 1743727)
+++ docs/release-notes/1.8.html	(working copy)
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" 
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" 
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
 <html xmlns="http://www.w3.org/1999/xhtml";>
 <head>
@@ -417,7 +417,7 @@
 one massive response.</p>
 
 <p>The main benefit of skelta mode is that it allows a correctly set up Apache
-server or intermediate proxy server to cache <tt>mod_dav_svn</tt>’s responses to
+server or intermediate proxy server to cache <tt>mod_dav_svn</tt>’s responses to
 handle later requests from the cache. This results in improved performance of
 svn client operations and reduced CPU usage on the server side. It also allows
 a more detailed audit of clients accessing resources in a Subversion
@@ -437,9 +437,8 @@
 
 <p>This release introduces two options to control if the svn client will use
 skelta or bulk update mode.</p>
-<p>
 <ul>
-<li> For the server administrator: The <tt>SVNAllowBulkUpdates</tt> directive for
+<li>For the server administrator: The <tt>SVNAllowBulkUpdates</tt> directive for
 <tt>mod_dav_svn</tt> now accepts <tt>Prefer</tt>. This will advise the svn
 client to always use bulk update mode. All svn client versions with a default
 configuration (see table) will respect this preference.</li>
@@ -451,7 +450,6 @@
 set to <tt>Prefer</tt>), and bulk updates mode with
 older servers and 1.8 servers which prefer bulk updates.</li>
 </ul>
-</p>
 
 <p>Table explaining the mode used between each combination of svn client and
 server version and relevant configuration directives:</p>
Index: docs/release-notes/1.9.html
===================================================================
--- docs/release-notes/1.9.html	(revision 1744020)
+++ docs/release-notes/1.9.html	(working copy)
@@ -1055,7 +1055,7 @@
   
 <p>Packing now takes a cache size parameter (<tt>-M</tt>) which is used for
 efficient operation on <a href="#fsfs-format7">FSFS format 7 repositories</a>.
-<p>
+</p>
 
 <pre>
   $ svnadmin pack -M 1000 /path/to/repository
@@ -1116,7 +1116,7 @@
 
 <p>The new <tt>delrevprop</tt> command deletes a revision property from either
 a revision or a transaction.  It complements <tt>setrevprop</tt> which adds
-or modifies revprops.</tt>
+or modifies revprops.</p>
 
 </div>  <!-- svnadmin-revprop -->
 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to