Author: dsahlberg
Date: Sat Sep 13 08:59:37 2025
New Revision: 1928405
Log:
In site/trunk
Additional HTML5 validation
* xdocs/guidelines.xml
Replace <tt> with <code>
* xdocs/versioning.xml
Remove background color from every second table row, it was anyway hidden
by the td background.
Remove deprecated <font size="-1">
Add section ids
Remove some <br />s
* docs/guidelines.html,
docs/versioning.html:
Generated from above
Modified:
apr/site/trunk/docs/guidelines.html
apr/site/trunk/docs/versioning.html
apr/site/trunk/xdocs/guidelines.xml
apr/site/trunk/xdocs/versioning.xml
Modified: apr/site/trunk/docs/guidelines.html
==============================================================================
--- apr/site/trunk/docs/guidelines.html Sat Sep 13 08:40:52 2025 (r1928404)
+++ apr/site/trunk/docs/guidelines.html Sat Sep 13 08:59:37 2025 (r1928405)
@@ -222,9 +222,9 @@ addressed.</p>
<div class="h2" id="votingprocedures">
<h2><strong>Voting Procedure Technicalities</strong></h2>
<blockquote>
-<p>Votes are tallied in the <tt>STATUS</tt> file, adjacent to the action item
-under vote. All votes must be either sent to the mailing list or added
-directly to the <tt>STATUS</tt> file entry for that action item.</p>
+<p>Votes are tallied in the <code>STATUS</code> file, adjacent to the action
+item under vote. All votes must be either sent to the mailing list or added
+directly to the <code>STATUS</code> file entry for that action item.</p>
</blockquote>
</div>
</blockquote>
Modified: apr/site/trunk/docs/versioning.html
==============================================================================
--- apr/site/trunk/docs/versioning.html Sat Sep 13 08:40:52 2025 (r1928404)
+++ apr/site/trunk/docs/versioning.html Sat Sep 13 08:59:37 2025 (r1928405)
@@ -140,40 +140,46 @@ will not be able to successfully link ag
<th>New Version</th>
<th>Compatible?</th>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>2.2.4</td>
- <td>Yes<br /><font size="-1">Compatibility across patch versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility across patch versions is guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>2.2.1</td>
- <td>Yes<br /><font size="-1">Compatibility across patch versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility across patch versions is guaranteed.
</td>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>2.3.1</td>
- <td>Yes<br /><font size="-1">Compatibility with later minor versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility with later minor versions is guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>2.1.7</td>
- <td>No<br /><font size="-1">Compatibility with prior minor versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with prior minor versions is not guaranteed.
</td>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>3.0.0</td>
- <td>No<br /><font size="-1">Compatibility with different major versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with different major versions is not guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>1.4.7</td>
- <td>No<br /><font size="-1">Compatibility with different major versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with different major versions is not guaranteed.
</td>
</tr>
</table>
@@ -187,7 +193,7 @@ APIs used by the application.</p>
<blockquote>
<p>This section details how we will build the code to meet the above
requirements and guidelines.</p>
-<div class="h2" id="">
+<div class="h2" id="patchversions">
<h2><strong>Patch Version</strong></h2>
<blockquote>
<p>To retain perfect source and binary compatibility, a patch release can only
@@ -197,7 +203,7 @@ public functions, or to the interpretati
releases.</p>
</blockquote>
</div>
-<div class="h2" id="">
+<div class="h2" id="minorversions">
<h2><strong>Minor Versions</strong></h2>
<blockquote>
<p>Minor releases can introduce new functions, new symbolic and enumerated
@@ -294,7 +300,7 @@ constants, and deprecate existing functi
</dd></dl>
</blockquote>
</div>
-<div class="h2" id="">
+<div class="h2" id="majorversions">
<h2><strong>Major Versions</strong></h2>
<blockquote>
<p>Any kind of change can be made during a major version release. Particular
@@ -315,19 +321,18 @@ types of changes that might occur:</p>
they are compiling against, or that is being used at runtime. Because of the
strict rules of source and binary compatibility, these checks can be simpler
and more complicated depending on what is needed.</p>
-<div class="h2" id="">
+<div class="h2" id="compiletimechecks">
<h2><strong>Compile-time Checks</strong></h2>
<blockquote>
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
<blockquote>
- <code>
+ <pre>
#define FOO_MAJOR_VERSION 1
- <br />
+
#define FOO_MINOR_VERSION 4
- <br />
- #define FOO_PATCH_VERSION 0
- </code>
+
+ #define FOO_PATCH_VERSION 0</pre>
</blockquote>
<p>The above symbols are the minimum required for this specification.</p>
<p>An application that desires, at compile-time, to decide on whether and how
@@ -344,7 +349,7 @@ application can support a wider variety
compile-time checks.</p>
</blockquote>
</div>
-<div class="h2" id="">
+<div class="h2" id="runtimechecks">
<h2><strong>Run-time Checks</strong></h2>
<blockquote>
<p>A library meeting this specification should support a way for an
@@ -381,7 +386,7 @@ detail how this versioning specification
to <a href="https://ometer.com/parallel.html">Havoc Pennington's
"Parallel Installation" essay</a> for futher details and the rationale behind this form of parallel
installation.</p>
-<div class="h2" id="">
+<div class="h2" id="librarynaming">
<h2><strong>Library Naming</strong></h2>
<blockquote>
<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
@@ -409,7 +414,7 @@ are relegated to the library name after
to generate <code>.so</code> libraries matching the above pattern. </p>
</blockquote>
</div>
-<div class="h2" id="">
+<div class="h2" id="includedirs">
<h2><strong>Include Directories</strong></h2>
<blockquote>
<p>The default installation directory for a library's include files should
@@ -429,7 +434,7 @@ include path and include the files norma
can simply include different versions of the include directory.</p>
</blockquote>
</div>
-<div class="h2" id="">
+<div class="h2" id="otherfiles">
<h2><strong>Other Files</strong></h2>
<blockquote>
<p><strong>NOTE:</strong> There is no recommendation at this time for the
Modified: apr/site/trunk/xdocs/guidelines.xml
==============================================================================
--- apr/site/trunk/xdocs/guidelines.xml Sat Sep 13 08:40:52 2025 (r1928404)
+++ apr/site/trunk/xdocs/guidelines.xml Sat Sep 13 08:59:37 2025 (r1928405)
@@ -185,9 +185,9 @@ addressed.</p>
<section id="votingprocedures">
<title>Voting Procedure Technicalities</title>
-<p>Votes are tallied in the <tt>STATUS</tt> file, adjacent to the action item
-under vote. All votes must be either sent to the mailing list or added
-directly to the <tt>STATUS</tt> file entry for that action item.</p>
+<p>Votes are tallied in the <code>STATUS</code> file, adjacent to the action
+item under vote. All votes must be either sent to the mailing list or added
+directly to the <code>STATUS</code> file entry for that action item.</p>
</section>
</section>
Modified: apr/site/trunk/xdocs/versioning.xml
==============================================================================
--- apr/site/trunk/xdocs/versioning.xml Sat Sep 13 08:40:52 2025 (r1928404)
+++ apr/site/trunk/xdocs/versioning.xml Sat Sep 13 08:59:37 2025 (r1928405)
@@ -87,46 +87,46 @@ will not be able to successfully link ag
<th>New Version</th>
<th>Compatible?</th>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>2.2.4</td>
- <td>Yes<br /><font size="-1"
- >Compatibility across patch versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility across patch versions is guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>2.2.1</td>
- <td>Yes<br /><font size="-1"
- >Compatibility across patch versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility across patch versions is guaranteed.
</td>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>2.3.1</td>
- <td>Yes<br /><font size="-1"
- >Compatibility with later minor versions is guaranteed.</font>
+ <td>Yes<br />
+ Compatibility with later minor versions is guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>2.1.7</td>
- <td>No<br /><font size="-1"
- >Compatibility with prior minor versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with prior minor versions is not guaranteed.
</td>
</tr>
- <tr valign="top" bgcolor="#e0e0e0">
+ <tr>
<td>2.2.3</td>
<td>3.0.0</td>
- <td>No<br /><font size="-1"
- >Compatibility with different major versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with different major versions is not guaranteed.
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2.2.3</td>
<td>1.4.7</td>
- <td>No<br /><font size="-1"
- >Compatibility with different major versions is not guaranteed.</font>
+ <td>No<br />
+ Compatibility with different major versions is not guaranteed.
</td>
</tr>
</table>
@@ -143,7 +143,7 @@ APIs used by the application.</p>
<p>This section details how we will build the code to meet the above
requirements and guidelines.</p>
-<section>
+<section id="patchversions">
<title>Patch Version</title>
<p>To retain perfect source and binary compatibility, a patch release can only
@@ -153,7 +153,7 @@ public functions, or to the interpretati
releases.</p>
</section>
-<section>
+<section id="minorversions">
<title>Minor Versions</title>
<p>Minor releases can introduce new functions, new symbolic and enumerated
@@ -252,7 +252,7 @@ constants, and deprecate existing functi
</section>
-<section>
+<section id="majorversions">
<title>Major Versions</title>
<p>Any kind of change can be made during a major version release. Particular
@@ -275,20 +275,19 @@ they are compiling against, or that is b
strict rules of source and binary compatibility, these checks can be simpler
and more complicated depending on what is needed.</p>
-<section>
+<section id="compiletimechecks">
<title>Compile-time Checks</title>
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
<blockquote>
- <code>
+ <pre>
#define FOO_MAJOR_VERSION 1
- <br />
+
#define FOO_MINOR_VERSION 4
- <br />
- #define FOO_PATCH_VERSION 0
- </code>
+
+ #define FOO_PATCH_VERSION 0</pre>
</blockquote>
<p>The above symbols are the minimum required for this specification.</p>
@@ -309,7 +308,7 @@ compile-time checks.</p>
</section>
-<section>
+<section id="runtimechecks">
<title>Run-time Checks</title>
<p>A library meeting this specification should support a way for an
@@ -350,7 +349,7 @@ to <a href="https://ometer.com/parallel.
"Parallel Installation" essay</a> for futher details and the rationale behind this form of parallel
installation.</p>
-<section>
+<section id="librarynaming">
<title>Library Naming</title>
<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
@@ -385,7 +384,7 @@ to generate <code>.so</code> libraries m
</section>
-<section>
+<section id="includedirs">
<title>Include Directories</title>
<p>The default installation directory for a library's include files should
@@ -410,7 +409,7 @@ can simply include different versions of
</section>
-<section>
+<section id="otherfiles">
<title>Other Files</title>
<p><strong>NOTE:</strong> There is no recommendation at this time for the
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.