Index: src/report.c
==================================================================
--- src/report.c
+++ src/report.c
@@ -749,11 +749,11 @@
 
   /* Output the separator above each entry in a table which has multiple lines
   ** per database entry.
   */
   if( pState->iNewRow>=0 ){
-    @ <tr><td colspan=%d(pState->nCol)><font size=1>&nbsp;</font></td></tr>
+    @ <tr><td colspan=%d(pState->nCol)>&nbsp;</td></tr>
   }
 
   /* Output the data for this entry from the database
   */
   zBg = pState->iBg>=0 ? azArg[pState->iBg] : 0;

Index: src/skins.c
==================================================================
--- src/skins.c
+++ src/skins.c
@@ -493,11 +493,11 @@
     }
   }
 
   style_header("Skins");
   if( zErr ){
-    @ <p><font color="red">%h(zErr)</font></p>
+    @ <p style="color:red">%h(zErr)</p>
   }
   @ <p>A "skin" is a combination of
   @ <a href="setup_skinedit?w=0">CSS</a>,
   @ <a href="setup_skinedit?w=2">Header</a>,
   @ <a href="setup_skinedit?w=1">Footer</a>, and

Index: src/stat.c
==================================================================
--- src/stat.c
+++ src/stat.c
@@ -412,13 +412,13 @@
     );
   }
   fsize = file_size(g.zRepositoryName);
   approxSizeName(sizeof(zBuf), zBuf, fsize);
   @ <h2>Repository Size: %s(zBuf)</h2>
-  @ <center><svg width='800' height='500'>
+  @ <svg class="statistics-report-pie-chart" width='800' height='500'>
   piechart_render(800,500,PIE_OTHER|PIE_PERCENT);
-  @ </svg></center>
+  @ </svg>
 
   if( g.localOpen ){
     db_multi_exec(
       "DROP TABLE temp.dbx;"
       "CREATE VIRTUAL TABLE temp.dbx USING dbstat(%s);"
@@ -441,11 +441,11 @@
       );
     }
     fsize = file_size(g.zLocalDbName);
     approxSizeName(sizeof(zBuf), zBuf, fsize);
     @ <h2>%h(file_tail(g.zLocalDbName)) Size: %s(zBuf)</h2>
-    @ <center><svg width='800' height='500'>
+    @ <svg class="statistics-report-pie-chart" width='800' height='500'>
     piechart_render(800,500,PIE_OTHER|PIE_PERCENT);
-    @ </svg></center>
+    @ </svg>
   }
   style_footer();
 }

Index: src/statrep.c
==================================================================
--- src/statrep.c
+++ src/statrep.c
@@ -339,13 +339,14 @@
     "CREATE TEMP TABLE piechart(amt,label);"
     "INSERT INTO piechart SELECT count(*), ifnull(euser,user) FROM v_reports"
                          " GROUP BY ifnull(euser,user) ORDER BY count(*) DESC;"
   );
   if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){
-    @ <center><svg width=700 height=400>
+    @ <svg class="statistics-report-pie-chart" width=700 height=400>
     piechart_render(700, 400, PIE_OTHER|PIE_PERCENT);
-    @ </svg></centre><hr/>
+    @ </svg>
+    @ <hr/>
   }
   @ <table class='statistics-report-table-events' border='0'
   @ cellpadding='2' cellspacing='0' id='statsTable'>
   @ <thead><tr>
   @ <th>User</th>
@@ -498,13 +499,14 @@
     "  WHEN 5 THEN 'Friday'"
     "  WHEN 6 THEN 'Saturday'"
     "  ELSE 'ERROR' END;", zUserName
   );
   if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){
-    @ <center><svg width=700 height=400>
+    @ <svg class="statistics-report-pie-chart" width=700 height=400>
     piechart_render(700, 400, PIE_OTHER|PIE_PERCENT);
-    @ </svg></centre><hr/>
+    @ </svg>
+    @ <hr/>
   }
   @ <table class='statistics-report-table-events' border='0'
   @ cellpadding='2' cellspacing='0' id='statsTable'>
   @ <thead><tr>
   @ <th>DoW</th>

Index: src/style.c
==================================================================
--- src/style.c
+++ src/style.c
@@ -1318,10 +1318,15 @@
   { "table.label-value th",
     "The label/value pairs on (for example) the ci page",
     @   vertical-align: top;
     @   text-align: right;
     @   padding: 0.2ex 2ex;
+  },
+  { ".statistics-report-pie-chart",
+    "for the /reports pie chart",
+    @   display: block;
+    @   margin: auto;
   },
   { ".statistics-report-graph-line",
     "for the /reports views",
     @   background-color: #446979;
   },
@@ -1429,10 +1434,15 @@
   { "span.snippet>mark",
     "Search markup",
     @ background-color: inherit;
     @ font-weight: bold;
   },
+  { ".search",
+    "Search form",
+    @ display: block;
+    @ margin: auto;
+  },
   { "div.searchForm",
     "Container for the search terms entry box",
     @ text-align: center;
   },
   { "p.searchEmpty",

Index: src/tkt.c
==================================================================
--- src/tkt.c
+++ src/tkt.c
@@ -423,11 +423,11 @@
 ** For trouble-shooting purposes, render a dump of the aField[] table to
 ** the webpage currently under construction.
 */
 static void showAllFields(void){
   int i;
-  @ <font color="blue">
+  @ <div style="color:blue">
   @ <p>Database fields:</p><ul>
   for(i=0; i<nField; i++){
     @ <li>aField[%d(i)].zName = "%h(aField[i].zName)";
     @ originally = "%h(aField[i].zValue)";
     @ currently = "%h(PD(aField[i].zName,""))";
@@ -652,15 +652,16 @@
   }
   needMod = ticket_need_moderation(0);
   if( g.zPath[0]=='d' ){
     const char *zNeedMod = needMod ? "required" : "skipped";
     /* If called from /debug_tktnew or /debug_tktedit... */
-    @ <font color="blue">
+    @ <div style="color:blue">
     @ <p>Ticket artifact that would have been submitted:</p>
     @ <blockquote><pre>%h(blob_str(&tktchng))</pre></blockquote>
     @ <blockquote><pre>Moderation would be %h(zNeedMod).</pre></blockquote>
-    @ <hr /></font>
+    @ </div>
+    @ <hr>
     return TH_OK;
   }else{
     if( g.thTrace ){
       Th_Trace("submit_ticket {\n<blockquote><pre>\n%h\n</pre></blockquote>\n"
                "}<br />\n",

Index: src/user.c
==================================================================
--- src/user.c
+++ src/user.c
@@ -472,11 +472,11 @@
     style_submenu_element("Newer", "Newer entries",
               "%s/access_log?o=%d&n=%d&y=%d", g.zTop, skip>=n ? skip-n : 0,
               n, y);
   }
   rc = db_prepare_ignore_error(&q, "%s", blob_sql_text(&sql));
-  @ <center><table border="1" cellpadding="5" id='logtable'>
+  @ <table border="1" cellpadding="5" id="logtable" align="center">
   @ <thead><tr><th width="33%%">Date</th><th width="34%%">User</th>
   @ <th width="33%%">IP Address</th></tr></thead><tbody>
   while( rc==SQLITE_OK && db_step(&q)==SQLITE_ROW ){
     const char *zName = db_column_text(&q, 0);
     const char *zIP = db_column_text(&q, 1);
@@ -497,11 +497,11 @@
   }
   if( skip>0 || cnt>n ){
     style_submenu_element("All", "All entries",
           "%s/access_log?n=10000000", g.zTop);
   }
-  @ </tbody></table></center>
+  @ </tbody></table>
   db_finalize(&q);
   @ <hr>
   @ <form method="post" action="%s(g.zTop)/access_log">
   @ <label><input type="checkbox" name="delold">
   @ Delete all but the most recent 200 entries</input></label>

Index: src/wikiformat.c
==================================================================
--- src/wikiformat.c
+++ src/wikiformat.c
@@ -1996,11 +1996,11 @@
 ** Attempt to reformat messy HTML to be easily readable by humans.
 **
 **    *  Try to keep lines less than 80 characters in length
 **    *  Collapse white space into a single space
 **    *  Put a blank line before:
-**          <blockquote><center><code><hN><p><pre><table>
+**          <blockquote><code><hN><p><pre><table>
 **    *  Put a newline after <br> and <hr>
 **    *  Start each of the following elements on a new line:
 **          <address><cite><dd><div><dl><dt><li><ol><samp>
 **          <tbody><td><tfoot><th><thead><tr><ul>
 **

Index: www/branching.wiki
==================================================================
--- www/branching.wiki
+++ www/branching.wiki
@@ -1,16 +1,17 @@
 <title>Branching, Forking, Merging, and Tagging</title>
+<style>table { margin: auto }</style>
 <h2>Background</h2>
 
 In a simple and perfect world, the development of a project would proceed
 linearly, as shown in figure 1.
 
-<center><table border=1 cellpadding=10 hspace=10 vspace=10>
+<table border=1 cellpadding=10 hspace=10 vspace=10>
 <tr><td align="center">
 <img src="branch01.gif" width=280 height=68><br>
 Figure 1
-</td></tr></table></center>
+</td></tr></table>
 
 Each circle represents a check-in.  For the sake of clarity, the check-ins
 are given small consecutive numbers.  In a real system, of course, the
 check-in numbers would be 40-character SHA1 hashes since it is not possible
 to allocate collision-free sequential numbers in a distributed system.
@@ -38,15 +39,15 @@
 
 Alas, reality often interferes with the simple linear development of a
 project.  Suppose two programmers make independent modifications to check-in 2.
 After both changes are committed, the check-in graph looks like figure 2:
 
-<center><table border=1 cellpadding=10 hspace=10 vspace=10>
+<table border=1 cellpadding=10 hspace=10 vspace=10>
 <tr><td align="center">
 <img src="branch02.gif" width=210 height=140><br>
 Figure 2
-</td></tr></table></center>
+</td></tr></table>
 
 The graph in figure 2 has two leaves: check-ins 3 and 4.  Check-in 2 has
 two children, check-ins 3 and 4.  We call this state a <i>fork</i>.
 
 Fossil tries to prevent forks. Suppose two programmers named Alice and
@@ -77,15 +78,15 @@
 To resolve this situation, Alice can use the fossil <b>merge</b> command
 to merge in Bob's changes in her local copy of check-in 3.  Then she
 can commit the results as check-in 5.  This results in a DAG as shown
 in figure 3.
 
-<center><table border=1 cellpadding=10 hspace=10 vspace=10>
+<table border=1 cellpadding=10 hspace=10 vspace=10>
 <tr><td align="center">
 <img src="branch03.gif" width=282 height=152><br>
 Figure 3
-</td></tr></table></center>
+</td></tr></table>
 
 Check-in 5 is a child of check-in 3 because it was created by editing
 check-in 3.  But check-in 5 also inherits the changes from check-in 4 by
 virtue of the merge.  So we say that check-in 5 is a <i>merge child</i>
 of check-in 4 and that it is a <i>direct child</i> of check-in 3.
@@ -124,15 +125,15 @@
 When multiple leaves are desirable, we call this <i>branching</i>
 instead of <i>forking</i>.
 Figure 4 shows an example of a project where there are two branches, one
 for development work and another for testing.
 
-<center><table border=1 cellpadding=10 hspace=10 vspace=10>
+<table border=1 cellpadding=10 hspace=10 vspace=10>
 <tr><td align="center">
 <img src="branch04.gif" width=426 height=123><br>
 Figure 4
-</td></tr></table></center>
+</td></tr></table>
 
 The hypothetical scenario of figure 4 is this:  The project starts and
 progresses to a point where (at check-in 2)
 it is ready to enter testing for its first release.
 In a real project, of course, there might be hundreds or thousands of
@@ -164,15 +165,15 @@
 
 Tags and properties are used in fossil to help express the intent, and
 thus to distinguish between forks and branches.  Figure 5 shows the
 same scenario as figure 4 but with tags and properties added:
 
-<center><table border=1 cellpadding=10 hspace=10 vspace=10>
+<table border=1 cellpadding=10 hspace=10 vspace=10>
 <tr><td align="center">
 <img src="branch05.gif" width=485 height=177><br>
 Figure 5
-</td></tr></table></center>
+</td></tr></table>
 
 A <i>tag</i> is a name that is attached to a check-in.  A
 <i>property</i> is a name/value pair.  Internally, fossil implements
 tags as properties with a NULL value.  So, tags and properties really
 are much the same thing, and henceforth we will use the word "tag"

Index: www/copyright-release.html
==================================================================
--- www/copyright-release.html
+++ www/copyright-release.html
@@ -74,12 +74,11 @@
 
 <p>By filling in the following information and signing your name,
 you agree to be bound by all of the terms
 set forth in this agreement.  Please print clearly.</p>
 
-<center>
-<p><table width="80%" border="1" cellpadding="0" cellspacing="0">
+<table width="80%" border="1" cellpadding="0" cellspacing="0" align="center">
 <tr><td width="20%" valign="top">Your name &amp email:</td><td width="80%">
 
     <!-- Replace this line with your name and email --> &nbsp;<p>&nbsp;
 
 </td></tr>
@@ -95,14 +94,13 @@
 
 </td></tr>
 <tr><td valign="top">Signature:</td><td>&nbsp;<p>&nbsp;</td></tr>
 <tr><td valign="top">Date:</td><td>&nbsp;<p>&nbsp;</td></tr>
 </table>
-</center>
 
 <p>Send completed forms to:
 <blockquote>
 Hipp, Wyrick &amp; Company, Inc.<br>
 6200 Maple Cove Lane<br>
 Charlotte, NC 28269-1086<br>
 USA
 </p>

Index: www/fossil-v-git.wiki
==================================================================
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -14,11 +14,11 @@
 might be biased in favor of Fossil.  Ask around with people who have
 used both Fossil and Git for other opinions.
 
 <h2>2.0 Executive Summary:</h2>
 
-<blockquote><center><table border=1 cellpadding=5>
+<blockquote><table border=1 cellpadding=5 align=center>
 <tr><th width="50%">GIT</th><th width="50%">FOSSIL</th></tr>
 <tr><td>File versioning only</td>
     <td>Versioning, Tickets, Wiki, and Technotes</td></tr>
 <tr><td>Sharding</td><td>Replicating</td></tr>
 <tr><td>Developer branches</td><td>Feature branches</td></tr>
@@ -29,11 +29,11 @@
     <td>Single-file relational database</td></tr>
 <tr><td>One check-out per repository</td>
     <td>Many check-outs per repository</td></tr>
 <tr><td>Uses "<tt>rebase</tt>"</td><td>Immutable</td></tr>
 <tr><td>GPL</td><td>BSD</td></tr>
-</table></center></blockquote>
+</table></blockquote>
 
 <h2>3.0 Discussion</h2>
 
 <h3>3.1 Feature Set</h3>
 

Index: www/index.wiki
==================================================================
--- www/index.wiki
+++ www/index.wiki
@@ -18,11 +18,11 @@
      <ul>
      <li> [http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-users | sign-up]
      <li> [http://www.mail-archive.com/fossil-users@lists.fossil-scm.org | archives]
      </ul>
 </ul>
-<center><img src="fossil3.gif"></center>
+<img src="fossil3.gif" style="margin:auto">
 </div>
 
 <p>Fossil is a simple, high-reliability, distributed software configuration
 management system with these advanced features:
 

Index: www/mkdownload.tcl
==================================================================
--- www/mkdownload.tcl
+++ www/mkdownload.tcl
@@ -31,26 +31,24 @@
 <a href='/fossil/ticket'>Tickets</a>
 <a href='/fossil/wiki'>Wiki</a>
 <a href='/download.html' class='active'>Download</a>
 </div>
 <div class="content">
-<p>
-
-<center><font size=4>}
+<p style="font-size:1.2em; text-align:center">}
 puts $out \
 "<b>To install Fossil &rarr;</b> download the stand-alone executable"
 puts $out \
 {and put it on your $PATH.
-</font><p><small>
+</p>
+<p style="text-align:center">
 RPMs available
 <a href="http://download.opensuse.org/repositories/home:/rmax:/fossil/">
 here.</a>
 Cryptographic checksums for download files are
 <a href="http://www.hwaci.com/fossil_download_checksums.html">here</a>.
-</small></p>
-</center>
-
+</p>
+<hr>
 <table cellpadding="10">
 }
 
 # Find all all unique timestamps.
 #
@@ -62,12 +60,12 @@
 
 # Do all versions from newest to oldest
 #
 foreach vers [lsort -decr -real [array names avers]] {
   set hr "/fossil/timeline?c=version-$vers;y=ci"
-  puts $out "<tr><td colspan=6 align=left><hr>"
-  puts $out "<center><b><a href=\"$hr\">Version $vers</a></b></center>"
+  puts $out "<tr><td colspan=6 align=center>"
+  puts $out "<b><a href=\"$hr\">Version $vers</a></b>"
   puts $out "</td></tr>"
   puts $out "<tr>"
 
   foreach {prefix suffix img desc} {
     fossil-linux-x86 zip linux.gif {Linux 3.x x86}

Index: www/mkindex.tcl
==================================================================
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -85,16 +85,14 @@
 set out [open permutedindex.html w]
 fconfigure $out -encoding utf-8 -translation lf
 puts $out \
 "<div class='fossil-doc' data-title='Index Of Fossil Documentation'>"
 puts $out {
-<center>
-<form action='../../../docsrch' method='GET'>
+<form class="search" action='../../../docsrch' method='GET'>
 <input type="text" name="s" size="40" autofocus>
 <input type="submit" value="Search Docs">
 </form>
-</center>
 <h2>Primary Documents:</h2>
 <ul>
 <li> <a href='quickstart.wiki'>Quick-start Guide</a>
 <li> <a href='faq.wiki'>FAQ</a>
 <li> <a href='build.wiki'>Compiling and installing Fossil</a>

Index: www/password.wiki
==================================================================
--- www/password.wiki
+++ www/password.wiki
@@ -133,11 +133,11 @@
 able to authenticate to the server.
 
 The client normally gets the login and password from the "remote URL".
 
 <blockquote><pre>
-http://<font color="blue">login:password</font>@servername.org/path
+http://<span style="color:blue">login:password</span>@servername.org/path
 </pre></blockquote>
 
 For older clients, the password is used for the shared secret as stated
 in the URL and with no encoding.
 For newer clients, the shared secret is derived from the password
@@ -145,11 +145,11 @@
 described above.  However, if the first character of the password is
 "*" (ASCII 0x2a) then the "*" is skipped and the rest of the password
 is used directly as the share secret without the SHA1 encoding.
 
 <blockquote><pre>
-http://<font color="blue">login:*password</font>@servername.org/path
+http://<span style="color:blue">login:*password</span>@servername.org/path
 </pre></blockquote>
 
 This *-before-the-password trick can be used by newer clients to
 sync against a legacy server that does not understand the new SHA1
 password encoding.

Index: www/permutedindex.html
==================================================================
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -1,13 +1,11 @@
 <div class='fossil-doc' data-title='Index Of Fossil Documentation'>
 
-<center>
-<form action='../../../docsrch' method='GET'>
+<form class="search" action='../../../docsrch' method='GET'>
 <input type="text" name="s" size="40" autofocus>
 <input type="submit" value="Search Docs">
 </form>
-</center>
 <h2>Primary Documents:</h2>
 <ul>
 <li> <a href='quickstart.wiki'>Quick-start Guide</a>
 <li> <a href='faq.wiki'>FAQ</a>
 <li> <a href='build.wiki'>Compiling and installing Fossil</a>

Index: www/sync.wiki
==================================================================
--- www/sync.wiki
+++ www/sync.wiki
@@ -385,11 +385,11 @@
 </blockquote>
 
 <p>As of [/timeline?r=trunk&c=2015-03-19+03%3A57%3A46&n=20|2015-03-19], the configuration-name must be one of the
 following values:
 
-<center><table border=0>
+<table border=0 align="center">
 <tr><td valign="top">
 <ul>
 <li> css
 <li> header
 <li> footer
@@ -436,11 +436,11 @@
 <li> @reportfmt
 <li> @user
 <li> @concealed
 <li> @shun
 </ul></td></tr>
-</table></center>
+</table>
 
 <p>New configuration-names are likely to be added in future releases of
 Fossil.  If the server receives a configuration-name that it does not
 understand, the entire reqconfig card is silently ignored.  The reqconfig
 card might also be ignored if the user lacks sufficient privilege to

Index: www/tech_overview.wiki
==================================================================
--- www/tech_overview.wiki
+++ www/tech_overview.wiki
@@ -65,11 +65,11 @@
 SQLite's [http://www.sqlite.org/lang_attach.html | ATTACH] command.
 
 The chart below provides a quick summary of how each of these
 database files are used by Fossil, with detailed discussion following.
 
-<center><table border="1" width="80%" cellpadding="0">
+<table border="1" width="80%" cellpadding="0" align="center">
 <tr>
 <td width="33%" valign="top">
 <h3 align="center">Configuration Database<br>"~/.fossil"</h3>
 <ul>
 <li>Global [/help/setting |settings]
@@ -103,11 +103,10 @@
 <li>Information needed to "[/help/undo|undo]" or "[/help/redo|redo]"
 </ul>
 </td>
 </tr>
 </table>
-</center>
 
 <h3>2.1 The Configuration Database</h3>
 
 The configuration database holds cross-repository preferences and a list of all
 repositories for a single user.