Author: brane
Date: Wed Sep 17 22:25:28 2025
New Revision: 1928570
Log:
Formatting tweaks: mostly lists, code snippets and title case.
Modified:
apr/site/trunk/docs/anonsvn.html
apr/site/trunk/docs/compiling_unix.html
apr/site/trunk/docs/compiling_win32.html
apr/site/trunk/docs/guidelines.html
apr/site/trunk/docs/versioning.html
apr/site/trunk/xdocs/anonsvn.xml
apr/site/trunk/xdocs/compiling_unix.xml
apr/site/trunk/xdocs/compiling_win32.xml
apr/site/trunk/xdocs/guidelines.xml
apr/site/trunk/xdocs/versioning.xml
Modified: apr/site/trunk/docs/anonsvn.html
==============================================================================
--- apr/site/trunk/docs/anonsvn.html Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/docs/anonsvn.html Wed Sep 17 22:25:28 2025 (r1928570)
@@ -82,53 +82,70 @@ difference is that you can't commit chan
access.</p>
<p>Anonymous Subversion access is available as follows:</p>
<dl>
-<dt>APR 2.0 (development version, incorporating both APR and APR-UTIL
-from earlier versions):</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/trunk/">https://svn.apache.org/repos/asf/apr/apr/trunk/</a> apr</dd>
-<dt>APR 1.6 (current release version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/">https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/</a> apr</dd>
-<dt>APR-UTIL 1.6 (current release version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/">https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/</a> apr</dd>
-<dt>APR 1.7 (incremental dev version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/">https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/</a> apr</dd>
-<dt>APR-UTIL 1.7 (incremental dev version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/">https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/</a> apr</dd>
-<dt>APR-ICONV</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/">https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/</a> apr-iconv</dd>
+<dt><p>APR 2.0 (development version, incorporating both APR and APR-util
+from earlier versions):</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/trunk/">https://svn.apache.org/repos/asf/apr/apr/trunk/</a> apr</code>
+</dd>
+
+<dt><p>APR 1.7 (current release version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/">https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/</a> apr</code>
+</dd>
+
+<dt><p>APR-util 1.6 (current release version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/">https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/</a> apr-util</code>
+</dd>
+
+<dt><p>APR 1.8 (incremental dev version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.8.x/">https://svn.apache.org/repos/asf/apr/apr/branches/1.8.x/</a> apr</code>
+</dd>
+
+<dt><p>APR-util 1.7 (incremental dev version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/">https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/</a> apr-util</code>
+</dd>
+
+<dt><p>APR-iconv</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/">https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/</a> apr-iconv</code>
+</dd>
</dl>
<p>You can also <a href="https://svn.apache.org/viewvc/apr/">browse the
repository using ViewVC</a>.</p>
</blockquote>
</div>
<div class="h1" id="sitesvn">
- <h1>Maintaining the site</h1>
+ <h1>Maintaining the Site</h1>
<blockquote>
<p>Developers can check out the site as follows:</p>
-<pre>
- svn co <a href="https://svn.apache.org/repos/asf/apr/site/trunk/">https://svn.apache.org/repos/asf/apr/site/trunk/</a> apr-site
-</pre>
+<blockquote>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/site/trunk/">https://svn.apache.org/repos/asf/apr/site/trunk/</a> apr-site</code>
+</blockquote>
<p>After generating HTML and committing, the site is updated
automatically via <code>rsync</code>.</p>
</blockquote>
</div>
<div class="h1" id="testsvn">
- <h1>Publishing test packages</h1>
+ <h1>Publishing Test Packages</h1>
<blockquote>
<p>Developers can check out the test package directory as follows:</p>
-<pre>
- svn co <a href="https://dist.apache.org/repos/dist/dev/apr/">https://dist.apache.org/repos/dist/dev/apr</a> apr-dev
-</pre>
+<blockquote>
+ <code>svn co <a href="https://dist.apache.org/repos/dist/dev/apr/">https://dist.apache.org/repos/dist/dev/apr</a> apr-dev</code>
+</blockquote>
<p>After committing, the site is updated automatically
via <code>svnpubsub</code>.</p>
</blockquote>
</div>
<div class="h1" id="releasesvn">
- <h1>Publishing releases</h1>
+ <h1>Publishing Releases</h1>
<blockquote>
<p>Developers can check out release directory as follows:</p>
-<pre>
- svn co <a href="https://dist.apache.org/repos/dist/release/apr/">https://dist.apache.org/repos/dist/release/apr</a> apr-release
-</pre>
+<blockquote>
+ <code>svn co <a href="https://dist.apache.org/repos/dist/release/apr/">https://dist.apache.org/repos/dist/release/apr</a> apr-release</code>
+</blockquote>
<p>After committing, the site is updated automatically
via <code>svnpubsub</code>.</p>
<p>Users access this directory via mirrors, and it takes around 24
Modified: apr/site/trunk/docs/compiling_unix.html
==============================================================================
--- apr/site/trunk/docs/compiling_unix.html Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/docs/compiling_unix.html Wed Sep 17 22:25:28 2025 (r1928570)
@@ -73,11 +73,11 @@
apr-util distribution tarballs requires nothing more than what
comes installed by default on various UNIX platforms.</p>
<p>All you should have to do is this:</p>
-<pre>
- ./configure
- make
- make install
-</pre>
+<blockquote><pre>
+./configure
+make
+make install
+</pre></blockquote>
<p>Note that if you are compiling directly from the Subversion repository,
you'll need GNU autoconf and GNU libtool installed, and you'll need
to run <code>./buildconf</code> before running the commands listed above.
@@ -110,9 +110,9 @@
<blockquote>
<p>The APR RPM can be built directly from the APR source tarball using
the following command:</p>
-<pre>
- rpmbuild -tb apr-1.4.x.tar.bz2
- </pre>
+<blockquote>
+ <code>rpmbuild -tb apr-1.4.x.tar.bz2</code>
+ </blockquote>
<p>Corresponding "-devel" packages will be required to be installed on your
build system prior to building the RPMs, the <code>rpmbuild</code> command
will automatically calculate what RPMs are required and will list any
@@ -128,13 +128,12 @@
<dt>apr-devel-1.4.x-1.i686.rpm</dt>
<dd>Headers and development files for the library.</dd>
-
</dl>
<p>An APR-Util RPM can be built directly from the APR-Util source
tarball using the following command:</p>
-<pre>
- rpmbuild -tb apr-util-1.4.x.tar.bz2
- </pre>
+<blockquote>
+ <code>rpmbuild -tb apr-util-1.4.x.tar.bz2</code>
+ </blockquote>
<p>If successful, the following RPMs will be created:</p>
<dl>
<dt>apr-util-1.4.x-1.i686.rpm</dt>
@@ -172,7 +171,6 @@
<dt>apr-util-nss-1.4.x-1.i686.rpm</dt>
<dd>Crypto NSS driver, dependent on Mozilla NSS.</dd>
-
</dl>
</blockquote>
</div>
Modified: apr/site/trunk/docs/compiling_win32.html
==============================================================================
--- apr/site/trunk/docs/compiling_win32.html Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/docs/compiling_win32.html Wed Sep 17 22:25:28 2025 (r1928570)
@@ -76,7 +76,7 @@ functional limitations.</p>
</blockquote>
</div>
<div class="h1" id="vstudio">
- <h1>Building APR with the included Visual Studio project files</h1>
+ <h1>Building APR with the Included Visual Studio Project Files</h1>
<blockquote>
<div class="h2" id="requirements">
<h2>Requirements</h2>
@@ -116,11 +116,11 @@ Workbench or Microsoft Development Envir
<blockquote>
<p>For a supported build, you must have apr, apr-iconv, and apr-util
checked-out in parallel directories. For example:</p>
-<ul>
- <li><code>C:\work\apr\</code></li>
- <li><code>C:\work\apr-iconv\</code></li>
- <li><code>C:\work\apr-util\</code></li>
-</ul>
+<blockquote><pre>
+C:\work\apr\
+C:\work\apr-iconv\
+C:\work\apr-util\
+</pre></blockquote>
<p>For a release, unzipping the release files into this directory layout
should be sufficient.</p>
<p>To track development, please read the information on <a href="anonsvn.html">checking out from Subversion</a>. We recommend <a href="https://tortoisesvn.net/">TortoiseSVN</a> on Win32 platforms.</p>
@@ -168,32 +168,32 @@ and apr-util. No exceptions.</p>
<h2>Command-Line Build</h2>
<blockquote>
<p>If you use the command line, you must configure it:</p>
-<pre>
- "C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
-</pre>
+<blockquote>
+ <code>"C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"</code>
+</blockquote>
<p>If necessary, you will also need to prepare the Platform SDK environment:</p>
-<pre>
- "C:\Program Files\Platform SDK\setenv.bat"
-</pre>
+<blockquote>
+ <code>"C:\Program Files\Platform SDK\setenv.bat"</code>
+</blockquote>
<p>cd to the apr-util directory. Now, simply use one of the following
commands to compile the static or dynamic libraries, respectively, on
Visual C++ 6.0 or later:</p>
-<pre>
- msdev aprutil.dsw /MAKE \
- apriconv - Win32 Release" \
- apr - Win32 Release" \
- libapr - Win32 Release" \
- gen_uri_delims - Win32 Release" \
- xml - Win32 Release" \
- "aprutil - Win32 Release" \
+<blockquote><pre>
+msdev aprutil.dsw /MAKE \
+ apriconv - Win32 Release" \
+ apr - Win32 Release" \
+ libapr - Win32 Release" \
+ gen_uri_delims - Win32 Release" \
+ xml - Win32 Release" \
+ "aprutil - Win32 Release"
- msdev aprutil.dsw /MAKE \
- libapr - Win32 Release" \
- libapriconv - Win32 Release" \
- gen_uri_delims - Win32 Release" \
- xml - Win32 Release" \
- libaprutil - Win32 Release" \
-</pre>
+msdev aprutil.dsw /MAKE \
+ libapr - Win32 Release" \
+ libapriconv - Win32 Release" \
+ gen_uri_delims - Win32 Release" \
+ xml - Win32 Release" \
+ libaprutil - Win32 Release"
+</pre></blockquote>
<p>Either command will compile APR. The latter will build the libraries as
.dll dynamic shared libraries, rather than static libraries.</p>
<p>Replace <code>Release</code> with <code>Debug</code> to include debugging
@@ -249,9 +249,9 @@ and apr-util. No exceptions.</p>
C++ 5.0 (97) will recognize them. To quickly prepare the .dsp files in
the native Visual Studio 5.0 (97) format, you can run this command
from the top-level apr directory (above apr, apr-util and apr-iconv):</p>
-<pre>
- perl apr\build\cvtdsp.pl -5
-</pre>
+<blockquote>
+ <code>perl apr\build\cvtdsp.pl -5</code>
+</blockquote>
<p>You must type this command from the <em>top level</em> directory of the apr
source tree. Every VC6 .dsp project file within the current directory and
below will be listed as it is converted. If you contribute back a patch that
Modified: apr/site/trunk/docs/guidelines.html
==============================================================================
--- apr/site/trunk/docs/guidelines.html Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/docs/guidelines.html Wed Sep 17 22:25:28 2025 (r1928570)
@@ -107,7 +107,7 @@ Then Commit" (RTC) process.</p>
</blockquote>
</div>
<div class="h1" id="changesentries">
- <h1>CHANGES entries</h1>
+ <h1>CHANGES Entries</h1>
<blockquote>
<p>The goals for CHANGES entries are to provide this documentation
for user-visible changes and to limit this documentation to releases
@@ -122,7 +122,7 @@ entry is appropriate at all).</p>
</blockquote>
</div>
<div class="h1" id="branchmaintenance">
- <h1>Branch maintenance</h1>
+ <h1>Branch Maintenance</h1>
<blockquote>
<p>Many changes which are committed to trunk are also delivered to other
branches. The procedure used is outlined below.</p>
@@ -160,15 +160,13 @@ longevity in dev/doc/admin ability and i
<div class="h1" id="decisionmaking">
<h1>Decision Making: Consensus and Voting</h1>
<blockquote>
-<dl>
- <dt><strong>NOTE:</strong></dt>
- <dd>
+<p class="note">
+ <strong>Note</strong>:
The following text describes the precise rules and procedure
for voting and decision making. In general, the behavior
embodied in these rules is part of the "gestalt" of the group,
and the formal use of these processes is not required.
- </dd>
- </dl>
+</p>
<p>Whenever possible, decisions are made by consensus. Consensus is reached
when both the following conditions are met: a committer indicates that
consensus has been reached, and no committer claims that consensus has not yet
@@ -192,10 +190,10 @@ ballot choices as desired -- that is, th
the voter "approves." Each vote is one of: </p>
<ul>
- <li>+1 : Yes, agree that the choice should be performed.</li>
- <li>+0 : Seems fine, but I can live without it</li>
- <li>-0 : Doesn't seem right, but I won't argue against it</li>
- <li>-1 : No, I am against this choice being performed.</li>
+ <li><code>+1</code> : Yes, agree that the choice should be performed.</li>
+ <li><code>+0</code> : Seems fine, but I can live without it</li>
+ <li><code>-0</code> : Doesn't seem right, but I won't argue against it</li>
+ <li><code>-1</code> : No, I am against this choice being performed.</li>
</ul>
</blockquote>
Modified: apr/site/trunk/docs/versioning.html
==============================================================================
--- apr/site/trunk/docs/versioning.html Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/docs/versioning.html Wed Sep 17 22:25:28 2025 (r1928570)
@@ -233,12 +233,12 @@ constants, and deprecate existing functi
</dd>
<dt>New constants</dt>
- <dd>Similar to functions, all of the original (old) constants will be
+ <dd><p>Similar to functions, all of the original (old) constants will be
available to an application. An application can then choose to use
- new constants to pick up new semantics and features.</dd>
+ new constants to pick up new semantics and features.</p></dd>
<dt>Replacing functions</dt>
- <dd>This gets a bit trickier. The original function
+ <dd><p>This gets a bit trickier. The original function
<strong>must</strong> remain available at the link-level so that an
application compiled against a minor version will continue to work
with later minor versions. Further, if an application is
@@ -246,7 +246,7 @@ constants, and deprecate existing functi
don't want to suddenly change the requirements for that application.
This means that the headers cannot silently map an old function
into a newer function, as that would turn an application, say,
- based on 1.2 into an application requiring the 1.4 or later release.
+ based on 1.2 into an application requiring the 1.4 or later release.</p>
<p>This means that functions cannot truly be replaced. The new,
alternate function can be made available in the header and
@@ -270,12 +270,12 @@ constants, and deprecate existing functi
</dd>
<dt>Deprecating functions</dt>
- <dd>Since a function must remain available for applications coded
+ <dd><p>Since a function must remain available for applications coded
against a previous minor release, it is only possible to
"<em>deprecate</em>" a function. It <strong>cannot</strong> be
removed from the headers (so that source compatibility is retained)
and it cannot be removed from the library (so that binary
- compatibility is retained).
+ compatibility is retained).</p>
<p>If you deprecate a function in APR, please mark it as such in the
function documentation, using the doxygen "<code>\deprecated</code>"
@@ -295,7 +295,8 @@ constants, and deprecate existing functi
<p>Note that all deprecated functions will be removed at the next
major version bump.</p>
- </dd></dl>
+ </dd>
+ </dl>
</blockquote>
</div>
<div class="h2" id="majorversions">
@@ -320,15 +321,15 @@ 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>
<div class="h2" id="compiletimechecks">
- <h2>Compile-time Checks</h2>
+ <h2>Compile-Time Checks</h2>
<blockquote>
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
-<blockquote>
- <pre>#define FOO_MAJOR_VERSION 1
+<blockquote><pre>
+#define FOO_MAJOR_VERSION 1
#define FOO_MINOR_VERSION 4
-#define FOO_PATCH_VERSION 0</pre>
-</blockquote>
+#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
to use a particular library feature needs to only check two values: the major
@@ -345,7 +346,7 @@ compile-time checks.</p>
</blockquote>
</div>
<div class="h2" id="runtimechecks">
- <h2>Run-time Checks</h2>
+ <h2>Run-Time Checks</h2>
<blockquote>
<p>A library meeting this specification should support a way for an
application to determine the library's version at <em>run-time</em>. This will
@@ -396,10 +397,10 @@ time, both applications' needs can be sa
<p>Typically, shared libraries on Unix-ish platforms will set up symlinks from
the <code>.so</code> library to specific versions of that library. For example:
</p>
-<blockquote>
- <pre>libFOO-MAJOR.so -> libFOO-MAJOR.so.0
-libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</pre>
-</blockquote>
+<blockquote><pre>
+libFOO-MAJOR.so -> libFOO-MAJOR.so.0
+libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH
+</pre></blockquote>
<p>In this configuration, applications will be bound to the <code>.so.0</code>
library. The minor version does not come into play here because we want
applications to dynamically load and link to the new library when a new minor
@@ -417,14 +418,14 @@ specify the <code>MAJOR</code> version n
a subdirectory in some standard location. For example:</p>
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <pre>/usr/include/FOO-MAJOR/</pre>
+ <code>/usr/include/FOO-MAJOR/</code>
</blockquote>
<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
-<blockquote>
- <pre>#include <FOO-stuff.h>
-#include <FOO-more.h></pre>
-</blockquote>
+<blockquote><pre>
+#include <FOO-stuff.h>
+#include <FOO-more.h>
+</pre></blockquote>
<p>Depending upon the API that the application is designed to work against, it
can simply include different versions of the include directory.</p>
</blockquote>
Modified: apr/site/trunk/xdocs/anonsvn.xml
==============================================================================
--- apr/site/trunk/xdocs/anonsvn.xml Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/xdocs/anonsvn.xml Wed Sep 17 22:25:28 2025 (r1928570)
@@ -24,25 +24,42 @@ access.</p>
<p>Anonymous Subversion access is available as follows:</p>
<dl>
-<dt>APR 2.0 (development version, incorporating both APR and APR-UTIL
-from earlier versions):</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/trunk/"
- >https://svn.apache.org/repos/asf/apr/apr/trunk/</a> apr</dd>
-<dt>APR 1.6 (current release version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/"
- >https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/</a> apr</dd>
-<dt>APR-UTIL 1.6 (current release version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/"
- >https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/</a> apr</dd>
-<dt>APR 1.7 (incremental dev version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/"
- >https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/</a> apr</dd>
-<dt>APR-UTIL 1.7 (incremental dev version)</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/"
- >https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/</a> apr</dd>
-<dt>APR-ICONV</dt>
-<dd>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/"
- >https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/</a> apr-iconv</dd>
+<dt><p>APR 2.0 (development version, incorporating both APR and APR-util
+from earlier versions):</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/trunk/"
+ >https://svn.apache.org/repos/asf/apr/apr/trunk/</a> apr</code>
+</dd>
+
+<dt><p>APR 1.7 (current release version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/"
+ >https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/</a> apr</code>
+</dd>
+
+<dt><p>APR-util 1.6 (current release version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/"
+ >https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/</a> apr-util</code>
+</dd>
+
+<dt><p>APR 1.8 (incremental dev version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr/branches/1.8.x/"
+ >https://svn.apache.org/repos/asf/apr/apr/branches/1.8.x/</a> apr</code>
+</dd>
+
+<dt><p>APR-util 1.7 (incremental dev version)</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/"
+ >https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/</a> apr-util</code>
+</dd>
+
+<dt><p>APR-iconv</p></dt>
+<dd>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/"
+ >https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/</a> apr-iconv</code>
+</dd>
</dl>
<p>You can also <a href="https://svn.apache.org/viewvc/apr/">browse the
@@ -51,42 +68,39 @@ repository using ViewVC</a>.</p>
</section>
<section id="sitesvn">
-<title>Maintaining the site</title>
+<title>Maintaining the Site</title>
<p>Developers can check out the site as follows:</p>
-
-<pre>
- svn co <a href="https://svn.apache.org/repos/asf/apr/site/trunk/"
- >https://svn.apache.org/repos/asf/apr/site/trunk/</a> apr-site
-</pre>
+<blockquote>
+ <code>svn co <a href="https://svn.apache.org/repos/asf/apr/site/trunk/"
+ >https://svn.apache.org/repos/asf/apr/site/trunk/</a> apr-site</code>
+</blockquote>
<p>After generating HTML and committing, the site is updated
automatically via <code>rsync</code>.</p>
</section>
<section id="testsvn">
-<title>Publishing test packages</title>
+<title>Publishing Test Packages</title>
<p>Developers can check out the test package directory as follows:</p>
-
-<pre>
- svn co <a href="https://dist.apache.org/repos/dist/dev/apr/"
- >https://dist.apache.org/repos/dist/dev/apr</a> apr-dev
-</pre>
+<blockquote>
+ <code>svn co <a href="https://dist.apache.org/repos/dist/dev/apr/"
+ >https://dist.apache.org/repos/dist/dev/apr</a> apr-dev</code>
+</blockquote>
<p>After committing, the site is updated automatically
via <code>svnpubsub</code>.</p>
</section>
<section id="releasesvn">
-<title>Publishing releases</title>
+<title>Publishing Releases</title>
<p>Developers can check out release directory as follows:</p>
-
-<pre>
- svn co <a href="https://dist.apache.org/repos/dist/release/apr/"
- >https://dist.apache.org/repos/dist/release/apr</a> apr-release
-</pre>
+<blockquote>
+ <code>svn co <a href="https://dist.apache.org/repos/dist/release/apr/"
+ >https://dist.apache.org/repos/dist/release/apr</a> apr-release</code>
+</blockquote>
<p>After committing, the site is updated automatically
via <code>svnpubsub</code>.</p>
Modified: apr/site/trunk/xdocs/compiling_unix.xml
==============================================================================
--- apr/site/trunk/xdocs/compiling_unix.xml Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/xdocs/compiling_unix.xml Wed Sep 17 22:25:28 2025 (r1928570)
@@ -15,11 +15,11 @@
<p>All you should have to do is this:</p>
-<pre>
- ./configure
- make
- make install
-</pre>
+<blockquote><pre>
+./configure
+make
+make install
+</pre></blockquote>
<p>Note that if you are compiling directly from the Subversion repository,
you'll need GNU autoconf and GNU libtool installed, and you'll need
@@ -59,9 +59,9 @@
<p>The APR RPM can be built directly from the APR source tarball using
the following command:</p>
- <pre>
- rpmbuild -tb apr-1.4.x.tar.bz2
- </pre>
+ <blockquote>
+ <code>rpmbuild -tb apr-1.4.x.tar.bz2</code>
+ </blockquote>
<p>Corresponding "-devel" packages will be required to be installed on your
build system prior to building the RPMs, the <code>rpmbuild</code> command
@@ -80,15 +80,14 @@
<dt>apr-devel-1.4.x-1.i686.rpm</dt>
<dd>Headers and development files for the library.</dd>
-
</dl>
<p>An APR-Util RPM can be built directly from the APR-Util source
tarball using the following command:</p>
- <pre>
- rpmbuild -tb apr-util-1.4.x.tar.bz2
- </pre>
+ <blockquote>
+ <code>rpmbuild -tb apr-util-1.4.x.tar.bz2</code>
+ </blockquote>
<p>If successful, the following RPMs will be created:</p>
@@ -128,7 +127,6 @@
<dt>apr-util-nss-1.4.x-1.i686.rpm</dt>
<dd>Crypto NSS driver, dependent on Mozilla NSS.</dd>
-
</dl>
</section>
Modified: apr/site/trunk/xdocs/compiling_win32.xml
==============================================================================
--- apr/site/trunk/xdocs/compiling_win32.xml Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/xdocs/compiling_win32.xml Wed Sep 17 22:25:28 2025 (r1928570)
@@ -17,7 +17,7 @@ functional limitations.</p>
</section>
<section id="vstudio">
-<title>Building APR with the included Visual Studio project files</title>
+<title>Building APR with the Included Visual Studio Project Files</title>
<section id="requirements">
<title>Requirements</title>
@@ -63,11 +63,11 @@ Workbench or Microsoft Development Envir
<p>For a supported build, you must have apr, apr-iconv, and apr-util
checked-out in parallel directories. For example:</p>
-<ul>
- <li><code>C:\work\apr\</code></li>
- <li><code>C:\work\apr-iconv\</code></li>
- <li><code>C:\work\apr-util\</code></li>
-</ul>
+<blockquote><pre>
+C:\work\apr\
+C:\work\apr-iconv\
+C:\work\apr-util\
+</pre></blockquote>
<p>For a release, unzipping the release files into this directory layout
should be sufficient.</p>
@@ -128,35 +128,37 @@ and apr-util. No exceptions.</p>
<title>Command-Line Build</title>
<p>If you use the command line, you must configure it:</p>
-<pre>
- "C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
-</pre>
+
+<blockquote>
+ <code>"C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"</code>
+</blockquote>
<p>If necessary, you will also need to prepare the Platform SDK environment:</p>
-<pre>
- "C:\Program Files\Platform SDK\setenv.bat"
-</pre>
+
+<blockquote>
+ <code>"C:\Program Files\Platform SDK\setenv.bat"</code>
+</blockquote>
<p>cd to the apr-util directory. Now, simply use one of the following
commands to compile the static or dynamic libraries, respectively, on
Visual C++ 6.0 or later:</p>
-<pre>
- msdev aprutil.dsw /MAKE \
- apriconv - Win32 Release" \
- apr - Win32 Release" \
- libapr - Win32 Release" \
- gen_uri_delims - Win32 Release" \
- xml - Win32 Release" \
- "aprutil - Win32 Release" \
-
- msdev aprutil.dsw /MAKE \
- libapr - Win32 Release" \
- libapriconv - Win32 Release" \
- gen_uri_delims - Win32 Release" \
- xml - Win32 Release" \
- libaprutil - Win32 Release" \
-</pre>
+<blockquote><pre>
+msdev aprutil.dsw /MAKE \
+ apriconv - Win32 Release" \
+ apr - Win32 Release" \
+ libapr - Win32 Release" \
+ gen_uri_delims - Win32 Release" \
+ xml - Win32 Release" \
+ "aprutil - Win32 Release"
+
+msdev aprutil.dsw /MAKE \
+ libapr - Win32 Release" \
+ libapriconv - Win32 Release" \
+ gen_uri_delims - Win32 Release" \
+ xml - Win32 Release" \
+ libaprutil - Win32 Release"
+</pre></blockquote>
<p>Either command will compile APR. The latter will build the libraries as
.dll dynamic shared libraries, rather than static libraries.</p>
@@ -221,9 +223,9 @@ and apr-util. No exceptions.</p>
C++ 5.0 (97) will recognize them. To quickly prepare the .dsp files in
the native Visual Studio 5.0 (97) format, you can run this command
from the top-level apr directory (above apr, apr-util and apr-iconv):</p>
-<pre>
- perl apr\build\cvtdsp.pl -5
-</pre>
+<blockquote>
+ <code>perl apr\build\cvtdsp.pl -5</code>
+</blockquote>
<p>You must type this command from the <em>top level</em> directory of the apr
source tree. Every VC6 .dsp project file within the current directory and
Modified: apr/site/trunk/xdocs/guidelines.xml
==============================================================================
--- apr/site/trunk/xdocs/guidelines.xml Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/xdocs/guidelines.xml Wed Sep 17 22:25:28 2025 (r1928570)
@@ -54,7 +54,7 @@ Then Commit" (RTC) process.</p>
</section>
<section id="changesentries">
-<title>CHANGES entries</title>
+<title>CHANGES Entries</title>
<p>The goals for CHANGES entries are to provide this documentation
for user-visible changes and to limit this documentation to releases
@@ -71,7 +71,7 @@ entry is appropriate at all).</p>
</section>
<section id="branchmaintenance">
-<title>Branch maintenance</title>
+<title>Branch Maintenance</title>
<p>Many changes which are committed to trunk are also delivered to other
branches. The procedure used is outlined below.</p>
@@ -116,15 +116,13 @@ longevity in dev/doc/admin ability and i
<section id="decisionmaking">
<title>Decision Making: Consensus and Voting</title>
- <dl>
- <dt><strong>NOTE:</strong></dt>
- <dd>
+<p class="note">
+ <strong>Note</strong>:
The following text describes the precise rules and procedure
for voting and decision making. In general, the behavior
embodied in these rules is part of the "gestalt" of the group,
and the formal use of these processes is not required.
- </dd>
- </dl>
+</p>
<p>Whenever possible, decisions are made by consensus. Consensus is reached
when both the following conditions are met: a committer indicates that
@@ -153,10 +151,10 @@ ballot choices as desired -- that is, th
the voter "approves." Each vote is one of: </p>
<ul>
- <li>+1 : Yes, agree that the choice should be performed.</li>
- <li>+0 : Seems fine, but I can live without it</li>
- <li>-0 : Doesn't seem right, but I won't argue against it</li>
- <li>-1 : No, I am against this choice being performed.</li>
+ <li><code>+1</code> : Yes, agree that the choice should be performed.</li>
+ <li><code>+0</code> : Seems fine, but I can live without it</li>
+ <li><code>-0</code> : Doesn't seem right, but I won't argue against it</li>
+ <li><code>-1</code> : No, I am against this choice being performed.</li>
</ul>
</blockquote>
Modified: apr/site/trunk/xdocs/versioning.xml
==============================================================================
--- apr/site/trunk/xdocs/versioning.xml Wed Sep 17 21:36:55 2025 (r1928569)
+++ apr/site/trunk/xdocs/versioning.xml Wed Sep 17 22:25:28 2025 (r1928570)
@@ -186,12 +186,12 @@ constants, and deprecate existing functi
</dd>
<dt>New constants</dt>
- <dd>Similar to functions, all of the original (old) constants will be
+ <dd><p>Similar to functions, all of the original (old) constants will be
available to an application. An application can then choose to use
- new constants to pick up new semantics and features.</dd>
+ new constants to pick up new semantics and features.</p></dd>
<dt>Replacing functions</dt>
- <dd>This gets a bit trickier. The original function
+ <dd><p>This gets a bit trickier. The original function
<strong>must</strong> remain available at the link-level so that an
application compiled against a minor version will continue to work
with later minor versions. Further, if an application is
@@ -199,7 +199,7 @@ constants, and deprecate existing functi
don't want to suddenly change the requirements for that application.
This means that the headers cannot silently map an old function
into a newer function, as that would turn an application, say,
- based on 1.2 into an application requiring the 1.4 or later release.
+ based on 1.2 into an application requiring the 1.4 or later release.</p>
<p>This means that functions cannot truly be replaced. The new,
alternate function can be made available in the header and
@@ -223,12 +223,12 @@ constants, and deprecate existing functi
</dd>
<dt>Deprecating functions</dt>
- <dd>Since a function must remain available for applications coded
+ <dd><p>Since a function must remain available for applications coded
against a previous minor release, it is only possible to
"<em>deprecate</em>" a function. It <strong>cannot</strong> be
removed from the headers (so that source compatibility is retained)
and it cannot be removed from the library (so that binary
- compatibility is retained).
+ compatibility is retained).</p>
<p>If you deprecate a function in APR, please mark it as such in the
function documentation, using the doxygen "<code>\deprecated</code>"
@@ -248,7 +248,8 @@ constants, and deprecate existing functi
<p>Note that all deprecated functions will be removed at the next
major version bump.</p>
- </dd></dl>
+ </dd>
+ </dl>
</section>
@@ -276,16 +277,16 @@ strict rules of source and binary compat
and more complicated depending on what is needed.</p>
<section id="compiletimechecks">
-<title>Compile-time Checks</title>
+<title>Compile-Time Checks</title>
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
-<blockquote>
- <pre>#define FOO_MAJOR_VERSION 1
+<blockquote><pre>
+#define FOO_MAJOR_VERSION 1
#define FOO_MINOR_VERSION 4
-#define FOO_PATCH_VERSION 0</pre>
-</blockquote>
+#define FOO_PATCH_VERSION 0
+</pre></blockquote>
<p>The above symbols are the minimum required for this specification.</p>
@@ -306,7 +307,7 @@ compile-time checks.</p>
</section>
<section id="runtimechecks">
-<title>Run-time Checks</title>
+<title>Run-Time Checks</title>
<p>A library meeting this specification should support a way for an
application to determine the library's version at <em>run-time</em>. This will
@@ -365,10 +366,10 @@ time, both applications' needs can be sa
the <code>.so</code> library to specific versions of that library. For example:
</p>
-<blockquote>
- <pre>libFOO-MAJOR.so -> libFOO-MAJOR.so.0
-libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</pre>
-</blockquote>
+<blockquote><pre>
+libFOO-MAJOR.so -> libFOO-MAJOR.so.0
+libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH
+</pre></blockquote>
<p>In this configuration, applications will be bound to the <code>.so.0</code>
library. The minor version does not come into play here because we want
@@ -390,16 +391,16 @@ a subdirectory in some standard location
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <pre>/usr/include/FOO-MAJOR/</pre>
+ <code>/usr/include/FOO-MAJOR/</code>
</blockquote>
<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
-<blockquote>
- <pre>#include <FOO-stuff.h>
-#include <FOO-more.h></pre>
-</blockquote>
+<blockquote><pre>
+#include <FOO-stuff.h>
+#include <FOO-more.h>
+</pre></blockquote>
<p>Depending upon the API that the application is designed to work against, it
can simply include different versions of the include directory.</p>
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.