Author: dsahlberg
Date: Sat Sep 13 08:24:34 2025
New Revision: 1928402
Log:
In site/trunk:
Continue HTML 5 cleanup:
- Replace custom <note> element rendered as a table with plain <p> and some CSS
- Replace <tt> element (deprecated) with <code>
- Replace deprecated html attribute align with inline css
* xdocs/compiling_win32.xml,
xdocs/index.xml,
xdocs/versioning.xml:
Update as described above
* xdoc/stylesheets/site.vsl
Remove (now) unused macro make_note
Remove (previously) unused macro source
* docs/style.css
Add the p.note class
* docs/compiling_win32.html,
docs/index.html,
docs/versioning.html:
Generated from the above
Modified:
apr/site/trunk/docs/compiling_win32.html
apr/site/trunk/docs/index.html
apr/site/trunk/docs/style.css
apr/site/trunk/docs/versioning.html
apr/site/trunk/xdocs/compiling_win32.xml
apr/site/trunk/xdocs/index.xml
apr/site/trunk/xdocs/stylesheets/site.vsl
apr/site/trunk/xdocs/versioning.xml
Modified: apr/site/trunk/docs/compiling_win32.html
==============================================================================
--- apr/site/trunk/docs/compiling_win32.html Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/docs/compiling_win32.html Sat Sep 13 08:24:34 2025 (r1928402)
@@ -100,8 +100,8 @@ functional limitations.</p>
<p>APR can be built using the <a href="#commandline">command line tools</a>, or
from within the <a href="#workspace">graphical IDE</a> (Visual Studio IDE
Workbench or Microsoft Development Environment).</p>
-<table border="1" cellpadding="5"><tr><td>
-<strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
+<p class="note">
+ <strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
Visual C++ 5.0 developers need the updated Microsoft Windows Platform SDK
to enable some APR features. The Platform SDK files distributed with
Visual C++ 6.0 and later are sufficient, so those users may skip this
@@ -110,8 +110,7 @@ Workbench or Microsoft Development Envir
issue warnings under MSVC++ 5.0 or fail to build entirely. Look for the
update on Microsoft's website - we are afraid they change the link too
often to cite.
-
-</td></tr></table>
+</p>
</blockquote>
</div>
<div class="h2" id="layout">
@@ -155,8 +154,7 @@ and apr-util. No exceptions.</p>
This workspace exposes the apr/apr.dsp static library and the
apr/test/aprtest.dsp projects that allow the developer to assemble the
entire test application suite.</p>
-<table border="1" cellpadding="5"><tr><td>
-
+<p class="note">
<strong>Historical Build Note</strong> (does not apply to releases after
1.1.1):
If you are doing a Visual Studio 5.0/6.0 Graphical build, it will only find
@@ -165,8 +163,7 @@ and apr-util. No exceptions.</p>
For Visual Studio .NET 2003 and newer, you may need to copy awk to the
Common7\Tools\Bin directory (i.e. where RC.exe is) - it no longer has the
specific PATH options (as far as we can tell).
-
-</td></tr></table>
+</p>
</blockquote>
</div>
<div class="h2" id="commandline">
@@ -204,15 +201,14 @@ and apr-util. No exceptions.</p>
<p>Replace <code>Release</code> with <code>Debug</code> to include debugging
information in the resulting files, making it easier to find bugs and
track down problems.</p>
-<table border="1" cellpadding="5"><tr><td>
-<strong>For Visual Studio C++ 5.0 command line users</strong>:
+<p class="note">
+ <strong>For Visual Studio C++ 5.0 command line users</strong>:
Only the .dsp files are maintained within Subversion. Win32 .mak
files are NOT maintained in Subversion, due to the tremendous waste
of reviewer's time. Therefore, you cannot rely on the NMAKE
commands above to build revised .dsp project files unless you then
export all .mak files yourself from the project.
-
-</td></tr></table>
+</p>
</blockquote>
</div>
<div class="h2" id="integrating">
Modified: apr/site/trunk/docs/index.html
==============================================================================
--- apr/site/trunk/docs/index.html Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/docs/index.html Sat Sep 13 08:24:34 2025 (r1928402)
@@ -107,10 +107,10 @@ libraries are</p>
<a href="https://www.apache.org/dist/apr/Announcement1.x.html">official announcement</a> as well as the
<a href="https://www.apache.org/dist/apr/CHANGES-APR-1.7">CHANGES-APR-1.7</a>
file.</p>
-<p align="center">
+<p style="text-align: center">
<a href="download.cgi">Download</a>
</p>
-<p align="center">
+<p style="text-align: center">
Programmer's Manual:
<a href="docs/apr/1.7/">APR</a>
</p>
@@ -126,17 +126,17 @@ Programmer's Manual:
Users of earlier versions are encouraged to update to this release.
</p>
<p>The main changes in this release are concerned with the third-party
-dependencies, including unbundling <tt>expat</tt>, and building with
-up-to-date versions of libraries such as <tt>OpenSSL</tt>
-and <tt>MySQL</tt>.
+dependencies, including unbundling <code>expat</code>, and building with
+up-to-date versions of libraries such as <code>OpenSSL</code>
+and <code>MySQL</code>.
</p>
<p>For further details of this release, see the
<a href="https://www.apache.org/dist/apr/Announcement-aprutil-1.x.html">official announcement</a> as well as the
<a href="https://www.apache.org/dist/apr/CHANGES-APR-UTIL-1.6">CHANGES-APR-UTIL-1.6</a> file.</p>
-<p align="center">
+<p style="text-align: center">
<a href="download.cgi">Download</a>
</p>
-<p align="center">
+<p style="text-align: center">
Programmer's Manual:
<a href="docs/apr-util/1.6/">APR-util</a>
</p>
Modified: apr/site/trunk/docs/style.css
==============================================================================
--- apr/site/trunk/docs/style.css Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/docs/style.css Sat Sep 13 08:24:34 2025 (r1928402)
@@ -1,6 +1,10 @@
a {
color: #525D76;
}
+p.note {
+ border-style: double;
+ padding: 5px;
+}
#logo {
padding: 8px;
}
Modified: apr/site/trunk/docs/versioning.html
==============================================================================
--- apr/site/trunk/docs/versioning.html Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/docs/versioning.html Sat Sep 13 08:24:34 2025 (r1928402)
@@ -94,11 +94,11 @@ next.</p>
<h1><strong>The Basics</strong></h1>
<blockquote>
<p> Versions are denoted using a standard triplet of integers:
-<tt><strong>MAJOR.MINOR.PATCH</strong></tt>. The basic intent is that
-<tt><strong>MAJOR</strong></tt> versions are incompatible, large-scale upgrades
-of the API. <tt><strong>MINOR</strong></tt> versions retain source and binary
+<code><strong>MAJOR.MINOR.PATCH</strong></code>. The basic intent is that
+<code><strong>MAJOR</strong></code> versions are incompatible, large-scale upgrades
+of the API. <code><strong>MINOR</strong></code> versions retain source and binary
compatibility with older minor versions, and changes in the
-<tt><strong>PATCH</strong></tt> level are perfectly compatible, forwards and
+<code><strong>PATCH</strong></code> level are perfectly compatible, forwards and
backwards.</p>
<p> It is important to note that a library that has not reached 1.0.0 is
<strong>not</strong> subject to the guidelines described in this document.
@@ -321,13 +321,13 @@ and more complicated depending on what i
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
<blockquote>
- <tt>
+ <code>
#define FOO_MAJOR_VERSION 1
<br />
#define FOO_MINOR_VERSION 4
<br />
#define FOO_PATCH_VERSION 0
- </tt>
+ </code>
</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
@@ -349,8 +349,8 @@ compile-time checks.</p>
<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
-usually be emboded as a simple function which returns the <tt>MAJOR</tt>,
-<tt>MINOR</tt>, and <tt>PATCH</tt> triplet in some form.</p>
+usually be emboded as a simple function which returns the <code>MAJOR</code>,
+<code>MINOR</code>, and <code>PATCH</code> triplet in some form.</p>
<p>Run-time checks are preferable in all cases. This type of check enables an
application to run against a wider variety of minor releases of a library (the
application is "<em>less coupled</em>" to a particular library release). Of
@@ -384,46 +384,46 @@ installation.</p>
<div class="h2" id="">
<h2><strong>Library Naming</strong></h2>
<blockquote>
-<p>On Unix-ish platforms, the library name should include the <tt>MAJOR</tt>
+<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
version number: </p>
-<blockquote><tt>libFOO-MAJOR.so</tt></blockquote>
+<blockquote><code>libFOO-MAJOR.so</code></blockquote>
<p>This strategy allows an application to explicitly state which version
of the library that it wants to link against. If the application was built for
-version 2 of the API, then it can link against <tt>libFOO-2.so</tt>. If another
+version 2 of the API, then it can link against <code>libFOO-2.so</code>. If another
application was built against version 3 of the API, then it links against
-<tt>libFOO-3.so</tt>. Since both libraries can reside on the system at the same
+<code>libFOO-3.so</code>. Since both libraries can reside on the system at the same
time, both applications' needs can be satisfied.</p>
<p>Typically, shared libraries on Unix-ish platforms will set up symlinks from
-the <tt>.so</tt> library to specific versions of that library. For example:
+the <code>.so</code> library to specific versions of that library. For example:
</p>
<blockquote>
- <tt>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
- libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</tt>
+ <code>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
+ libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</code>
</blockquote>
-<p>In this configuration, applications will be bound to the <tt>.so.0</tt>
+<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
-version is installed. Thus, the <tt>MINOR</tt> and the <tt>PATCH</tt> values
-are relegated to the library name after the <tt>.so.0</tt> portion.</p>
+version is installed. Thus, the <code>MINOR</code> and the <code>PATCH</code> values
+are relegated to the library name after the <code>.so.0</code> portion.</p>
<p>The implication here is that build systems for libraries should arrange
-to generate <tt>.so</tt> libraries matching the above pattern. </p>
+to generate <code>.so</code> libraries matching the above pattern. </p>
</blockquote>
</div>
<div class="h2" id="">
<h2><strong>Include Directories</strong></h2>
<blockquote>
<p>The default installation directory for a library's include files should
-specify the <tt>MAJOR</tt> version number, and should normally be installed as
+specify the <code>MAJOR</code> version number, and should normally be installed as
a subdirectory in some standard location. For example:</p>
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <tt>/usr/include/FOO-MAJOR/</tt>
+ <code>/usr/include/FOO-MAJOR/</code>
</blockquote>
-<p>An application can place the <tt>FOO-MAJOR</tt> directory on its
+<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
<blockquote>
- <tt>#include <FOO-stuff.h><br />
- #include <FOO-more.h></tt>
+ <code>#include <FOO-stuff.h><br />
+ #include <FOO-more.h></code>
</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>
@@ -433,9 +433,9 @@ can simply include different versions of
<h2><strong>Other Files</strong></h2>
<blockquote>
<p><strong>NOTE:</strong> There is no recommendation at this time for the
-best and proper handling of, say, <tt>FOO-config</tt> types of files. Or
+best and proper handling of, say, <code>FOO-config</code> types of files. Or
non-code types of files (e.g. things that typically get installed into areas
-like <tt>/usr/shared</tt>).</p>
+like <code>/usr/shared</code>).</p>
<p>Further thought and exploration is needed here.</p>
</blockquote>
</div>
Modified: apr/site/trunk/xdocs/compiling_win32.xml
==============================================================================
--- apr/site/trunk/xdocs/compiling_win32.xml Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/xdocs/compiling_win32.xml Sat Sep 13 08:24:34 2025 (r1928402)
@@ -43,7 +43,8 @@ functional limitations.</p>
from within the <a href="#workspace">graphical IDE</a> (Visual Studio IDE
Workbench or Microsoft Development Environment).</p>
-<note><strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
+<p class="note">
+ <strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
Visual C++ 5.0 developers need the updated Microsoft Windows Platform SDK
to enable some APR features. The Platform SDK files distributed with
Visual C++ 6.0 and later are sufficient, so those users may skip this
@@ -52,7 +53,7 @@ Workbench or Microsoft Development Envir
issue warnings under MSVC++ 5.0 or fail to build entirely. Look for the
update on Microsoft's website - we are afraid they change the link too
often to cite.
-</note>
+</p>
</section>
@@ -110,7 +111,7 @@ and apr-util. No exceptions.</p>
apr/test/aprtest.dsp projects that allow the developer to assemble the
entire test application suite.</p>
-<note>
+<p class="note">
<strong>Historical Build Note</strong> (does not apply to releases after
1.1.1):
If you are doing a Visual Studio 5.0/6.0 Graphical build, it will only find
@@ -119,7 +120,7 @@ and apr-util. No exceptions.</p>
For Visual Studio .NET 2003 and newer, you may need to copy awk to the
Common7\Tools\Bin directory (i.e. where RC.exe is) - it no longer has the
specific PATH options (as far as we can tell).
-</note>
+</p>
</section>
@@ -164,13 +165,14 @@ and apr-util. No exceptions.</p>
information in the resulting files, making it easier to find bugs and
track down problems.</p>
-<note><strong>For Visual Studio C++ 5.0 command line users</strong>:
+<p class="note">
+ <strong>For Visual Studio C++ 5.0 command line users</strong>:
Only the .dsp files are maintained within Subversion. Win32 .mak
files are NOT maintained in Subversion, due to the tremendous waste
of reviewer's time. Therefore, you cannot rely on the NMAKE
commands above to build revised .dsp project files unless you then
export all .mak files yourself from the project.
-</note>
+</p>
</section>
<section id="integrating">
Modified: apr/site/trunk/xdocs/index.xml
==============================================================================
--- apr/site/trunk/xdocs/index.xml Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/xdocs/index.xml Sat Sep 13 08:24:34 2025 (r1928402)
@@ -48,11 +48,11 @@ libraries are</p>
<a href="https://www.apache.org/dist/apr/CHANGES-APR-1.7" >CHANGES-APR-1.7</a>
file.</p>
-<p align="center">
+<p style="text-align: center">
<a href="download.cgi">Download</a>
</p>
-<p align="center">
+<p style="text-align: center">
Programmer's Manual:
<a href="docs/apr/1.7/">APR</a>
</p>
@@ -70,9 +70,9 @@ Programmer's Manual:
Users of earlier versions are encouraged to update to this release.
</p>
<p>The main changes in this release are concerned with the third-party
-dependencies, including unbundling <tt>expat</tt>, and building with
-up-to-date versions of libraries such as <tt>OpenSSL</tt>
-and <tt>MySQL</tt>.
+dependencies, including unbundling <code>expat</code>, and building with
+up-to-date versions of libraries such as <code>OpenSSL</code>
+and <code>MySQL</code>.
</p>
@@ -82,11 +82,11 @@ and <tt>MySQL</tt>.
<a href="https://www.apache.org/dist/apr/CHANGES-APR-UTIL-1.6"
>CHANGES-APR-UTIL-1.6</a> file.</p>
-<p align="center">
+<p style="text-align: center">
<a href="download.cgi">Download</a>
</p>
-<p align="center">
+<p style="text-align: center">
Programmer's Manual:
<a href="docs/apr-util/1.6/">APR-util</a>
</p>
Modified: apr/site/trunk/xdocs/stylesheets/site.vsl
==============================================================================
--- apr/site/trunk/xdocs/stylesheets/site.vsl Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/xdocs/stylesheets/site.vsl Sat Sep 13 08:24:34 2025 (r1928402)
@@ -68,41 +68,11 @@ $table
#end
##
##
-#macro ( make_note $note)
-<table border="1" cellpadding="5"><tr><td>
-$note
-</td></tr></table>
-#end
-##
-##
#macro ( metaauthor $author $email )
<meta name="author" content="$author"><meta name="email" content="$email">
#end
##
##
-#macro ( source $value )
-<div align="left">
- <table cellspacing="4" cellpadding="0" border="0">
- <tr>
- <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- </tr>
- <tr>
- <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- <td bgcolor="#ffffff"><pre>$escape.getText($value.getText())</pre></td>
- <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- </tr>
- <tr>
- <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td>
- </tr>
- </table>
-</div>
-#end
-##
-##
#macro ( section $section $level )
#if ($section.getChild("title"))
#set ($heading = $section.getChildText("title"))
@@ -130,12 +100,8 @@ $note
##end
## Second, output the section-level children with transformers
#foreach ( $items in $section.getChildren() )
-#if ($items.getName().equals("source"))
-#source ($items)
-#elseif ($items.getName().equals("table"))
+#if ($items.getName().equals("table"))
#color_table ($items)
-#elseif ($items.getName().equals("note"))
-#make_note ($items.getContent())
#elseif ($items.getName().equals("section"))
#set ($sublevel = $level + 1)
#section ($items $sublevel)
Modified: apr/site/trunk/xdocs/versioning.xml
==============================================================================
--- apr/site/trunk/xdocs/versioning.xml Sat Sep 13 06:45:02 2025 (r1928401)
+++ apr/site/trunk/xdocs/versioning.xml Sat Sep 13 08:24:34 2025 (r1928402)
@@ -34,11 +34,11 @@ next.</p>
<title>The Basics</title>
<p> Versions are denoted using a standard triplet of integers:
-<tt><strong>MAJOR.MINOR.PATCH</strong></tt>. The basic intent is that
-<tt><strong>MAJOR</strong></tt> versions are incompatible, large-scale upgrades
-of the API. <tt><strong>MINOR</strong></tt> versions retain source and binary
+<code><strong>MAJOR.MINOR.PATCH</strong></code>. The basic intent is that
+<code><strong>MAJOR</strong></code> versions are incompatible, large-scale upgrades
+of the API. <code><strong>MINOR</strong></code> versions retain source and binary
compatibility with older minor versions, and changes in the
-<tt><strong>PATCH</strong></tt> level are perfectly compatible, forwards and
+<code><strong>PATCH</strong></code> level are perfectly compatible, forwards and
backwards.</p>
<p> It is important to note that a library that has not reached 1.0.0 is
@@ -282,13 +282,13 @@ and more complicated depending on what i
constants. For example:</p>
<blockquote>
- <tt>
+ <code>
#define FOO_MAJOR_VERSION 1
<br />
#define FOO_MINOR_VERSION 4
<br />
#define FOO_PATCH_VERSION 0
- </tt>
+ </code>
</blockquote>
<p>The above symbols are the minimum required for this specification.</p>
@@ -314,8 +314,8 @@ compile-time checks.</p>
<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
-usually be emboded as a simple function which returns the <tt>MAJOR</tt>,
-<tt>MINOR</tt>, and <tt>PATCH</tt> triplet in some form.</p>
+usually be emboded as a simple function which returns the <code>MAJOR</code>,
+<code>MINOR</code>, and <code>PATCH</code> triplet in some form.</p>
<p>Run-time checks are preferable in all cases. This type of check enables an
application to run against a wider variety of minor releases of a library (the
@@ -353,35 +353,35 @@ installation.</p>
<section>
<title>Library Naming</title>
-<p>On Unix-ish platforms, the library name should include the <tt>MAJOR</tt>
+<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
version number: </p>
-<blockquote><tt>libFOO-MAJOR.so</tt></blockquote>
+<blockquote><code>libFOO-MAJOR.so</code></blockquote>
<p>This strategy allows an application to explicitly state which version
of the library that it wants to link against. If the application was built for
-version 2 of the API, then it can link against <tt>libFOO-2.so</tt>. If another
+version 2 of the API, then it can link against <code>libFOO-2.so</code>. If another
application was built against version 3 of the API, then it links against
-<tt>libFOO-3.so</tt>. Since both libraries can reside on the system at the same
+<code>libFOO-3.so</code>. Since both libraries can reside on the system at the same
time, both applications' needs can be satisfied.</p>
<p>Typically, shared libraries on Unix-ish platforms will set up symlinks from
-the <tt>.so</tt> library to specific versions of that library. For example:
+the <code>.so</code> library to specific versions of that library. For example:
</p>
<blockquote>
- <tt>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
- libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</tt>
+ <code>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
+ libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</code>
</blockquote>
-<p>In this configuration, applications will be bound to the <tt>.so.0</tt>
+<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
-version is installed. Thus, the <tt>MINOR</tt> and the <tt>PATCH</tt> values
-are relegated to the library name after the <tt>.so.0</tt> portion.</p>
+version is installed. Thus, the <code>MINOR</code> and the <code>PATCH</code> values
+are relegated to the library name after the <code>.so.0</code> portion.</p>
<p>The implication here is that build systems for libraries should arrange
-to generate <tt>.so</tt> libraries matching the above pattern. </p>
+to generate <code>.so</code> libraries matching the above pattern. </p>
</section>
@@ -389,20 +389,20 @@ to generate <tt>.so</tt> libraries match
<title>Include Directories</title>
<p>The default installation directory for a library's include files should
-specify the <tt>MAJOR</tt> version number, and should normally be installed as
+specify the <code>MAJOR</code> version number, and should normally be installed as
a subdirectory in some standard location. For example:</p>
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <tt>/usr/include/FOO-MAJOR/</tt>
+ <code>/usr/include/FOO-MAJOR/</code>
</blockquote>
-<p>An application can place the <tt>FOO-MAJOR</tt> directory on its
+<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
<blockquote>
- <tt>#include <FOO-stuff.h><br />
- #include <FOO-more.h></tt>
+ <code>#include <FOO-stuff.h><br />
+ #include <FOO-more.h></code>
</blockquote>
<p>Depending upon the API that the application is designed to work against, it
@@ -414,9 +414,9 @@ can simply include different versions of
<title>Other Files</title>
<p><strong>NOTE:</strong> There is no recommendation at this time for the
-best and proper handling of, say, <tt>FOO-config</tt> types of files. Or
+best and proper handling of, say, <code>FOO-config</code> types of files. Or
non-code types of files (e.g. things that typically get installed into areas
-like <tt>/usr/shared</tt>).</p>
+like <code>/usr/shared</code>).</p>
<p>Further thought and exploration is needed here.</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.