From 2c80b54110a744f2c168083894c794830fa90b23 Mon Sep 17 00:00:00 2001
From: Andrew Johnson <anj@aps.anl.gov>
Date: Wed, 6 Oct 2010 11:41:49 -0500
Subject: [PATCH] docs: Replaced non-ascii space characters.

---
 documentation/BuildingR3.13AppsWithR3.14.html |  20 +--
 .../BuildingR3.13ExtensionsWithR3.14.html     | 158 ++++++++----------
 .../ConvertingR3.14.5AppsToR3.14.6.html       |  36 ++--
 documentation/ReleaseChecklist.html           |  72 ++++----
 4 files changed, 139 insertions(+), 147 deletions(-)

diff --git a/documentation/BuildingR3.13AppsWithR3.14.html b/documentation/BuildingR3.13AppsWithR3.14.html
index f5f2e1fca..2a5b04492 100644
--- a/documentation/BuildingR3.13AppsWithR3.14.html
+++ b/documentation/BuildingR3.13AppsWithR3.14.html
@@ -15,7 +15,7 @@
 
 <p><br>
 This document describes how to modify a R3.13 vxWorks application so that it
-builds with release R3.14.  It describes an easy way to modify
+builds with release R3.14. It describes an easy way to modify
 applications subject to the following restrictions:</p>
 <ul>
   <li>The application still uses config rules rather than the configure rules
@@ -42,7 +42,7 @@ to remove all files and directories created by earlier builds.
 
 <h3>Update RELEASE</h3>
 
-<p>Change  the <tt>EPICS_BASE</tt> definition to point to the R3.14 base
+<p>Change the <tt>EPICS_BASE</tt> definition to point to the R3.14 base
 release. All hardware support and some soft support is now unbundled. For
 example the sequencer is unbundled. You must obtain and build all required
 unbundled products before you can build the application. The location of each
@@ -141,7 +141,7 @@ to
 
 <h3>recGbl calls</h3>
 
-<p>You may need to add the line  "<tt>#include "recGbl.h</tt>" to any source
+<p>You may need to add the line "<tt>#include "recGbl.h</tt>" to any source
 files that have recGbl* calls so that the file will compile without
 errors.</p>
 
@@ -164,9 +164,9 @@ and add
 to your application src/Makefile.
 
 <p>You should consider changing any existing old steppermotor records to the
-new EPICS  <a
+new EPICS <a
 href="http://www.aps.anl.gov/upd/people/sluiter/epics/modules/mechanism/motor/index.html">motor
-record</a>  module supported by Beamline Controls and Data Acquisition at
+record</a> module supported by Beamline Controls and Data Acquisition at
 APS.</p>
 
 <h3>RecDynLink.o and devPtSoft changes</h3>
@@ -178,14 +178,14 @@ them in base.dbd and baseLIBOBJS if they are not used in application.</p>
 
 <p>All hardware support (dev, drv and dbd files) has been unbundled from base
 R3.14. This support includes the files <tt>symb, symb.dbd, drvHp1404a.o,
-drvEpvxiMsg.o, and drvEpvxi.o</tt>.  If they are not used in your
+drvEpvxiMsg.o, and drvEpvxi.o</tt>. If they are not used in your
 application, comment out references to these files in base.dbd and
 baseLIBOBJS.</p>
 
 <p>Hardware support files now exist as separate modules available for
 download from the <a href="http://www.aps.anl.gov/epics/">EPICS www home page
 at ANL</a>. You must now download all the hardware support modules needed for
-your application, build the modules with R3.14 base,  add the appropriate
+your application, build the modules with R3.14 base, add the appropriate
 module full path definitions to your application config/RELEASE file, and
 change <tt>LIBOBJS</tt> location definition <tt>$(EPICS_BASE_BIN)</tt> to the
 module definition bin directory in your application src directory files.</p>
@@ -201,9 +201,9 @@ into your application config/RELEASE file .
 
 <p>After a gnumake in the symb module followed by a gnumake in the
 application config directory, the definitions <tt>SYMB_BIN</tt> and
-<tt>SYMB_LIB</tt> will be created,  the directory $(SYMB)/include will be
-added to the include directories on the compiler command lines  (in the
-<tt>INSTALL_INCLUDES</tt> definition)  and the directory $(SYMB)/dbd will be
+<tt>SYMB_LIB</tt> will be created, the directory $(SYMB)/include will be
+added to the include directories on the compiler command lines (in the
+<tt>INSTALL_INCLUDES</tt> definition) and the directory $(SYMB)/dbd will be
 added to the dbd search directories on the dbExpand command lines (in the
 <tt>INSTALL_DBDFLAGS</tt> definition).</p>
 
diff --git a/documentation/BuildingR3.13ExtensionsWithR3.14.html b/documentation/BuildingR3.13ExtensionsWithR3.14.html
index 998ac0300..02271a4ce 100644
--- a/documentation/BuildingR3.13ExtensionsWithR3.14.html
+++ b/documentation/BuildingR3.13ExtensionsWithR3.14.html
@@ -34,7 +34,7 @@ directory.</p>
 <blockquote>
   <ul>
     <li>Download the latest version of the extensions/config files,
-      extensionsConfig.tar.gz,  from the APS EPICS www page.</li>
+      extensionsConfig.tar.gz, from the APS EPICS www page.</li>
       The extensions directory can have both the base/config (for extensions with
       R3.13 makefiles) and base/configure (for extensions with R3.14 makefiles)
       directories.
@@ -43,7 +43,7 @@ directory.</p>
     variable.</li>
     <li>Set EPICS_BASE in extensions/config/RELEASE to the full path location
       of a built R3.14 base.</li>
-    <li>BASE_3_14 is now defined in the base/config/CONFIG_BASE_VERSION.  The
+    <li>BASE_3_14 is now defined in the base/config/CONFIG_BASE_VERSION. The
       commented BASE_3_14 definition can be removed from
       extensions/config/RELEASE.</li>
   </ul>
@@ -77,82 +77,80 @@ directory.</p>
   removing Db), the following lines should be added to Makefile.Host.</p>
 
   <blockquote>
-    <tt>ifdef BASE_3_14</tt> <br>
-    <tt>USR_LIBS += dbStaticHost</tt> <br>
-    <tt>dbStaticHost_DIR = $(EPICS_BASE_LIB)</tt> <br>
-    <tt>else</tt> <br>
-    <tt>USR_LIBS += Db</tt> <br>
-    <tt>Db_DIR = $(EPICS_BASE_LIB)</tt> <br>
-    <tt>endif</tt></blockquote>
+    <pre>ifdef BASE_3_14
+USR_LIBS += dbStaticHost
+dbStaticHost_DIR = $(EPICS_BASE_LIB)
+else
+USR_LIBS += Db
+Db_DIR = $(EPICS_BASE_LIB)
+endif</pre></blockquote>
 
   <li><b>Library dbStaticHost names changed</b></li>
 
-  <p>Library functions have been renamed.  If there are calls with old db
+  <p>Library functions have been renamed. If there are calls with old db
   names, add the following lines</p>
 
   <blockquote>
-    <tt>#if  EPICS_REVISION &amp;&amp; EPICS_REVISION == 13</tt> <br>
-    <tt>#define dbFindRecordType    dbFindRecdes</tt> <br>
-    <tt>#define dbGetNRecordTypes   dbGetNRecdes</tt> <br>
-    <tt>#define dbNextRecordType    dbNextRecdes</tt> <br>
-    <tt>#define dbFirstField        dbFirstFielddes</tt> <br>
-    <tt>#define dbGetRecordTypeName dbGetRecdesName</tt> <br>
-    <tt>#define dbFirstRecordType   dbFirstRecdes</tt> <br>
-    <tt>#define dbNextField         dbNextFielddes</tt> <br>
-    <tt>#define dbGetMenuChoices    dbGetChoices</tt><tt></tt>
+    <pre>#if  EPICS_REVISION &amp;&amp; EPICS_REVISION == 13
+#define dbFindRecordType    dbFindRecdes
+#define dbGetNRecordTypes   dbGetNRecdes
+#define dbNextRecordType    dbNextRecdes
+#define dbFirstField        dbFirstFielddes
+#define dbGetRecordTypeName dbGetRecdesName
+#define dbFirstRecordType   dbFirstRecdes
+#define dbNextField         dbNextFielddes
+#define dbGetMenuChoices    dbGetChoices
 
-    <p><tt>long dbReadDatabaseFP(</tt> <br>
-    <tt>    DBBASE **ppdbbase,FILE *fp, const char *path,const char
-    *substitutions)</tt> <br>
-    <tt>{</tt> <br>
-    <tt>     return(dbRead(*ppdbbase,fp));</tt> <br>
-    <tt>}</tt> <br>
-    <tt>#endif</tt></p>
-  </blockquote>
-  and  change the the old names and function calls to the R3.14 versions:
+long dbReadDatabaseFP(DBBASE **ppdbbase,
+    FILE *fp, const char *path,const char *substitutions)
+{
+     return(dbRead(*ppdbbase,fp));
+}
+#endif
+</pre></blockquote>
+  and change the the old names and function calls to the R3.14 versions:
 
   <blockquote>
-    <tt>dbFindRecdes         =&gt;  dbFindRecordType</tt> <br>
-    <tt>dbGetNRecdes         =&gt;  dbGetNRecordTypes</tt> <br>
-    <tt>dbNextRecdes         =&gt;  dbNextRecordType</tt> <br>
-    <tt>dbFirstFielddes      =&gt;  dbFirstField</tt> <br>
-    <tt>dbGetRecdesName      =&gt;  dbGetRecordTypeName</tt> <br>
-    <tt>dbFirstRecdes        =&gt;  dbFirstRecordType</tt> <br>
-    <tt>dbNextFielddes       =&gt;  dbNextField</tt> <br>
-    <tt>dbGetChoices         =&gt;  dbGetMenuChoices</tt> <br>
-    <tt>dbRead(pdbbase,fp)   =&gt;  dbReadDatabaseFP(&amp;pdbbase,fp,0,0)</tt>
-
-    <p></p>
-  </blockquote>
-
+    <pre>dbFindRecdes         =&gt;  dbFindRecordType
+dbGetNRecdes         =&gt;  dbGetNRecordTypes
+dbNextRecdes         =&gt;  dbNextRecordType
+dbFirstFielddes      =&gt;  dbFirstField
+dbGetRecdesName      =&gt;  dbGetRecordTypeName
+dbFirstRecdes        =&gt;  dbFirstRecordType
+dbNextFielddes       =&gt;  dbNextField
+dbGetChoices         =&gt;  dbGetMenuChoices
+dbRead(pdbbase,fp)   =&gt;  dbReadDatabaseFP(&amp;pdbbase,fp,0,0)
+</pre></blockquote>
 
   <li><b>Target architecture specifications changed</b></li>
 
   <p>Since target architecture specifications have been changed (solaris to
   solaris-sparc, win32 to win32-x86, ...) Makefile.Host references to and
-  tests on T_A have to be changed.  In most cases T_A can be replaced by
-  OS_CLASS.  Since HOST_ARCH will eventually be phased out, it would be a
+  tests on T_A have to be changed. In most cases T_A can be replaced by
+  OS_CLASS. Since HOST_ARCH will eventually be phased out, it would be a
   good idea to change any Makefile.Host references to HOST_ARCH to OS_CLASS
   if possible. <br>
   For example change</p>
 
   <blockquote>
-    <tt>ifeq ($(T_A),solaris)</tt> <br>
-    <tt>RPCFLAGS = -K -1</tt> <br>
-    <tt>endif</tt></blockquote>
+    <pre>ifeq ($(T_A),solaris)
+RPCFLAGS = -K -1
+endif
+</pre></blockquote>
   to
 
   <blockquote>
-    <tt>ifeq ($(OS_CLASS),solaris)</tt> <br>
-    <tt>RPCFLAGS = -K -1</tt> <br>
-    <tt>endif</tt></blockquote>
+    <pre>ifeq ($(OS_CLASS),solaris)
+RPCFLAGS = -K -1
+endif
+</pre></blockquote>
 
 
   <li><b>New ca_set_puser</b></li>
 
   <p>Statements of the form: <tt>ca_puser(chid) = xyz</tt>; should to be
-  changed to:  <tt>ca_set_puser(chid,xyz)</tt>; <br>
-   </p>
+  changed to: <tt>ca_set_puser(chid,xyz)</tt>; <br>
+  </p>
 
 
   <li><b>Extern C around includes</b></li>
@@ -162,9 +160,10 @@ directory.</p>
   For example change</p>
 
   <blockquote>
-    <tt>extern "C" {</tt> <br>
-    <tt>#include "cadefs.h"</tt> <br>
-    <tt>} /* end extern C */</tt></blockquote>
+    <pre>extern "C" {
+#include "cadefs.h"
+} /* end extern C */
+</pre></blockquote>
   to
 
   <blockquote>
@@ -174,8 +173,8 @@ directory.</p>
 
   <p>Some infrequently used R3.13 timestamp functions and macro definitions
   have been removed from EPICS base and now exist in a library, ts, created
-  and installed in the ar extension.  The only ANL distributed extension that
-  uses these unbundled functions and macros  is cau. The two R3.13 functions
+  and installed in the ar extension. The only ANL distributed extension that
+  uses these unbundled functions and macros is cau. The two R3.13 functions
   tsStampToText and tsLocalTime along with the definitions TS_TEXT_MONDDYYYY
   and TS_TEXT_MMDDYY have been retained in R3.14 for extension compatibility
   purposes. <br>
@@ -185,27 +184,28 @@ directory.</p>
   PROD_LIBS or USR_LIBS in your Makefile.Host as follows:</p>
 
   <blockquote>
-    <tt>#include "tsSubr.h"</tt>
+    <pre>#include "tsSubr.h"
 
-    <p><tt>ifdef BASE_3_14</tt> <br>
-    <tt>PROD_LIBS += ts</tt> <br>
-    <tt>ts_DIR = $(EPICS_EXTENSIONS_LIB)</tt> <br>
-    <tt>endif</tt></p>
-  </blockquote>
+ifdef BASE_3_14
+PROD_LIBS += ts
+ts_DIR = $(EPICS_EXTENSIONS_LIB)
+endif
+</pre></blockquote>
 
   <li><b>No Field name length restriction</b></li>
 
   <p> The length restriction to database record names no longer exists in R3.14
-  so the the <tt>FLDNAME_SZ macro definition was removed.from dbDefs.h. 
+  so the the <tt>FLDNAME_SZ macro definition was removed.from dbDefs.h.
   Extensions which still have a field name restriction should add the field
   name size definition to their code until they are updated.</tt></p>
 
   <blockquote>
-    <tt>#ifndef FLDNAME_SZ</tt> <br>
-    <tt>#define FLDNAME_SZ 4  /*Field Name Size*/</tt> <br>
-    <tt>#endif</tt></blockquote>
+    <pre>#ifndef FLDNAME_SZ
+#define FLDNAME_SZ 4 /*Field Name Size*/
+#endif
+</pre></blockquote>
 
-  <li><b>Some EPICS base version macros removed</b></li>
+  <li><b>Some EPICS base version macros removed</b></li>
 
   <p>
   The EPICS base version macros that start with "BASE_" have been removed
@@ -214,24 +214,14 @@ directory.</p>
 </blockquote>
 
 <blockquote>
-
   <blockquote>
-    <tt></tt><font face="Arial,Helvetica">BASE_VERSION         
-            =&gt;  EPICS_VERSION</font> <br>
-    <font face="Arial,Helvetica">BASE_REVISION                  =&gt; 
-    EPICS_REVISION</font> <br>
-    <font face="Arial,Helvetica">BASE_MODIFICATION       =&gt; </font><font
-    face="Arial,Helvetica">  EPICS_MODIFICATION</font> <br>
-    <font face="Arial,Helvetica">BASE_UPDATE_NAME       =&gt; 
-    EPICS_UPDATE_NAME</font> <br>
-    <font face="Arial,Helvetica">BASE_UPDATE_LEVEL       =&gt;  
-    EPICS_UPDATE_LEVEL</font> <br>
-    <font face="Arial,Helvetica">BASE_VERSION_STRING   =&gt; 
-    EPICS_VERSION_STRING</font></blockquote>
+    BASE_VERSION            =&gt;  EPICS_VERSION
+    BASE_REVISION           =&gt;  EPICS_REVISION
+    BASE_MODIFICATION       =&gt;  EPICS_MODIFICATION
+    BASE_UPDATE_NAME        =&gt;  EPICS_UPDATE_NAME
+    BASE_UPDATE_LEVEL       =&gt;  EPICS_UPDATE_LEVEL
+    BASE_VERSION_STRING     =&gt;  EPICS_VERSION_STRING
+    </blockquote>
 </blockquote>
-
-<p></p>
-
-<p></p>
 </body>
 </html>
diff --git a/documentation/ConvertingR3.14.5AppsToR3.14.6.html b/documentation/ConvertingR3.14.5AppsToR3.14.6.html
index 494edbf87..1cf4dccca 100644
--- a/documentation/ConvertingR3.14.5AppsToR3.14.6.html
+++ b/documentation/ConvertingR3.14.5AppsToR3.14.6.html
@@ -86,27 +86,27 @@ compiler will issue warning messages and the ioc may issue the message:
 
 <h3>Record support changes</h3>
 
-<p>The steppermotor, scan, and pid records are no longer in base.  If these
+<p>The steppermotor, scan, and pid records are no longer in base. If these
 records are not used in your application, comment out references to them in
-base.dbd. If these record types are used at your site, they  should be
+base.dbd. If these record types are used at your site, they should be
 downloaded and built with base R3.14 by your EPICS administrator. To update
-the R3.14 location of these record types in your application you must  add
+the R3.14 location of these record types in your application you must add
 appropriate module definitions to your application's config/RELEASE file and
 add <tt>LIBOBJS</tt> definitions to the src Makefile.</p>
 
 <p>For example add</p>
 
-<p>         <tt>PID=&lt;full path to modules directory&gt;/pid</tt></p>
+<pre>    PID=&lt;full path to modules directory&gt;/pid
+</pre>
 
 <p>to config/RELEASE and add <br>
 
-<p></p>
-
-<p><tt>LIBOBJS += $(PID_BIN)/pidRecord.o</tt></p>
+<pre>    LIBOBJS += $(PID_BIN)/pidRecord.o
+</pre>
 to your application src/Makefile.
 
 <p>You should consider changing any existing old steppermotor records to the
-new EPICS  motor record  module supported by Beamline Controls and Data
+new EPICS motor record module supported by Beamline Controls and Data
 Acquisition at APS.</p>
 
 <h3>RecDynLink.o and devPtSoft changes</h3>
@@ -115,7 +115,7 @@ Acquisition at APS.</p>
 separate EPICS modules.You must now add the appropriate module full path
 definitions to your application config/RELEASE file, and change
 <tt>LIBOBJS</tt> location definition <tt>$(EPICS_BASE_BIN)</tt> to the module
-definition bin directory in your application src directory files.  See
+definition bin directory in your application src directory files. See
 "Hardware support changes" below for instructions.</p>
 
 <h3>Hardware support changes</h3>
@@ -129,21 +129,24 @@ application, comment out references to them in base.dbd.</p>
 support for your site should be downloaded and built with base R3.14 by your
 EPICS administrator. You must now add the appropriate module full path
 definitions to your application config/RELEASE file, and change
-<tt>LIBOBJS</tt> location from <tt>$(EPICS_BASE_BIN) </tt>to the module  bin
+<tt>LIBOBJS</tt> location from <tt>$(EPICS_BASE_BIN) </tt>to the module bin
 directory in your application src directory files.</p>
 
 <p>For example, remove</p>
 
-<p>         <tt>LIBOBJS+=$(EPICS_BASE_BIN)/symb</tt></p>
+<pre>    LIBOBJS+=$(EPICS_BASE_BIN)/symb
+</pre>
 
 <p>from baseLIBOBJS and add</p>
 
-<p>         <tt>LIBOBJS+=$(SYMB_BIN)/symb</tt></p>
+<pre>    LIBOBJS+=$(SYMB_BIN)/symb
+</pre>
 
 <p>to your application src/Makefile, <br>
 and add the line</p>
 
-<p><tt>SYMB=&lt;full path definition for the built module SYMB&gt;</tt></p>
+<pre>    SYMB=&lt;full path definition for the built module SYMB&gt;
+</pre>
 
 <p>into your application config/RELEASE file .</p>
 
@@ -151,13 +154,12 @@ and add the line</p>
 
 <p>The host tool dbLoadTemplate has been replace by a new EPICS extension,
 msi, which should be downloaded and built with base R3.14 by your EPICS
-administrator. dbLoadTemplate is still supported on iocs.  If, in your
+administrator. dbLoadTemplate is still supported on iocs. If, in your
 application, db files are created from template and substitution files you
-should  add the definition</p>
+should add the definition</p>
 
 <p><tt>MSI=&lt;full path name to msi executable&gt;</tt></p>
 
 <p>to your application config/RELEASE file.</p>
-<br>
- </body>
+</body>
 </html>
diff --git a/documentation/ReleaseChecklist.html b/documentation/ReleaseChecklist.html
index be587bd2e..6f4182cee 100644
--- a/documentation/ReleaseChecklist.html
+++ b/documentation/ReleaseChecklist.html
@@ -84,20 +84,20 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Preparing for a release</th>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Email all developers about the upcoming release and ask for a list
         of remaining jobs that must be finished.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>All developers</td>
       <td>Check the bug tracker for any outstanding items and handle
         appropriately. All bugs that have been fixed should have been marked
         as Fix Committed.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Set the Feature Freeze date, by which time all Bazaar commits for
         enhancements and new functionality should have been completed. After
@@ -105,7 +105,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
         during testing.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager<br />
         &amp; all developers</td>
       <td>Ensure that documentation will be updated before the release date:
@@ -118,12 +118,12 @@ relevent roles unless the Release Manager designates otherwise:</p>
       </td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Review and update this document for the upcoming release.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Create a release milestone on Launchpad if necessary and set the
         expected release date. Note that pre-release and release-candidate
@@ -133,13 +133,13 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Creating pre-release and release-candidate versions</th>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Edit and commit changes to the EPICS version number file
         configure/CONFIG_BASE_VERSION.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Tag the module in Bazaar, using these tag conventions:
         <ul>
@@ -159,7 +159,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
         </td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Export the tagged version into a tarfile. Note that this command
         generates a gzipped tarfile directly from the repository:
@@ -176,25 +176,25 @@ relevent roles unless the Release Manager designates otherwise:</p>
         </td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Test the tarfile by extracting its contents and building it on at
         least one supported platform.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Copy the tar file to the Base download area of the website.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Create or update a website subdirectory to hold the release
         documentation, and copy in selected files from the base/documentation
         and base/html directories of the tarfile.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Create or modify the webpage for the new release with links to the
         release documents and tar file. Pre-release and release-candidate
@@ -202,7 +202,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
         number.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Add the new tar file to the website Base download index page.</td>
       </tr>
@@ -210,7 +210,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Testing</th>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Platform Developers</td>
       <td>Run the built-in test programs on all available host platforms using
         <blockquote><tt>
@@ -218,20 +218,20 @@ relevent roles unless the Release Manager designates otherwise:</p>
         </tt></blockquote></td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Platform Developers</td>
       <td>Run the CA client side regression tests on all available host
         platforms.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Platform Developers</td>
       <td>Build and run the
         <a href="https://launchpad.net/epics-base-tests">epics-base-tests</a>
         suite on all available platforms.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Platform Developers</td>
       <td>Check that all makeBaseApp templates build and run properly, all
         <i>xxxApp</i> and <i>xxxBoot</i> types and any internal options, e.g.
@@ -239,20 +239,20 @@ relevent roles unless the Release Manager designates otherwise:</p>
         <tt>INSTALL_LOCATION</tt> in configure/CONFIG_SITE.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Platform Developers</td>
       <td>Build the SNL Sequencer against this version of Base, and check that
         the makeBaseApp example builds and runs correctly with it.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Application Developers</td>
       <td>Build external applications against this version of Base on all
         available platforms and test as appropriate.  Application code changes
         may be necessary where the EPICS Base APIs have been modified.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Check that documentation has been updated:
         <ul>
@@ -268,7 +268,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Release Approval</th>
     </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Obtain a positive <q>Ok to release</q> from all platform developers
         once a Release Candidate version has gone a whole week without any
@@ -278,13 +278,13 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Creating the final release version</th>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Edit and commit changes to the EPICS version number file
         configure/CONFIG_BASE_VERSION.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Tag the module in Bazaar:
         <blockquote><tt>
@@ -294,7 +294,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
         </td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Export the tagged version into a tarfile. Note that this command
         generates a gzipped tarfile directly from the repository:
@@ -311,7 +311,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
         </td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Test the tar file by extracting its contents and building it on at
         least one supported platform</td>
@@ -320,58 +320,58 @@ relevent roles unless the Release Manager designates otherwise:</p>
       <th colspan="3">Publish and Announce it</th>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Configuration Manager</td>
       <td>Copy the tar file to the Base download area of the website</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Update the website subdirectory that holds the release
         documentation, and copy in the files from the base/documentation
         directory of the tarfile.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Update the webpage for the new release with links to the release
         documents and tar file.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Add the new release tar file to the website Base download index
         page.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Link to the release webpage from other relevent areas of the
         website - update front page and sidebars.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Upload the release tar file to the Launchpad download area.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Add the new Version number to the Launchpad bug tracker.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Find all Launchpad bug reports with the status Fix Committed which
         have been fixed in this release and mark them Fix Released.</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Release Manager</td>
       <td>Email tech-talk</td>
       </tr>
     <tr>
-      <td> </td>
+      <td>&nbsp;</td>
       <td>Website Manager</td>
       <td>Add an entry to the website News page, linking to the new version
       webpage.</td>