Index: www/propaganda.html
===================================================================
--- www/propaganda.html	(revision 11305)
+++ www/propaganda.html	(working copy)
@@ -1,3 +1,5 @@
+<!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN"
+"http://style.tigris.org/tigris_transitional.dtd">
 <html>
 <head>
 <title>Subversion Propaganda</title>
@@ -196,23 +198,23 @@
   </ul>
 
 
-<a name="testimonials"><h3>Testimonials</h3></a>
+<h3><a name="testimonials">Testimonials</a></h3>
 
   <ul>
 
     <li>
     <strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=72516"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72516"
           >Ron Bieber</a></strong>
           <tt>(23&nbsp;July&nbsp;2004)</tt>
           <br/>
  
-      <em><p>I currently manage a group of about 20 developers for a
+      <p><em>I currently manage a group of about 20 developers for a
           Fortune 500 company.  We used CVS from January of 2001 until
           May of 2004 when we converted all of our repositories over
-          to Subversion.</p>
+          to Subversion.</em></p>
 
-      <p>The advantages we received from Subversion are immense.
+      <p><em>The advantages we received from Subversion are immense.
       Before our conversion to CVS from VSS, we had two full time
       employees managing our production builds.  Upon conversion to
       CVS we cut that resource count down to one.  This resource
@@ -223,24 +225,24 @@
       We had two CVS "experts" in house which included me and one of
       my direct reports.  We were constantly called in to resolve
       issues.  I myself spent a ton of time managing the support of
-      the CVS repositories.</p>
+      the CVS repositories.</em></p>
 
-      <p>After running across Subversion by chance in May of 2003, I
+      <p><em>After running across Subversion by chance in May of 2003, I
       started piloting it at home.  As I used it more, I became
       convinced that this was a tool that my team needed in order to
       increase our productivity.  After using it for a while, I was
       able to come up with some specific areas that justified our
       conversion to Subversion in order to maximize our productivity
-      and code quality:</p>
+      and code quality:</em></p>
 
       <ol>
 
-        <li>Atomic commits - The lack of atomicity in commits was a
+        <li><em>Atomic commits - The lack of atomicity in commits was a
         huge problem for us with CVS.  Subversion gives us the
         confidence that when we commit, everything went into the
-        repository.</li>
+        repository.</em></li>
 
-        <li>The ability to back out changes before going to
+        <li><em>The ability to back out changes before going to
         production--using an activity branching model, we can allow
         developers to branch per activity and only merge to the main
         source base after code reviews have been performed.  If there
@@ -251,9 +253,9 @@
         when an activity had to be removed from the build.  In CVS we
         had to go through each file looking for revisions that were
         effected by a change.  Subversion now manages this for
-        us.</li>
+        us.</em></li>
 
-        <li>Decreased build time.  We run CruiseControl, and the
+        <li><em>Decreased build time.  We run CruiseControl, and the
         checkout times we were experiencing with CVS, along with our
         requirement to tag of our source base after each build caused
         our automated build cycle to take an inordinate amount of
@@ -262,9 +264,9 @@
         stressful.  The cheap copy functionality of Subversion
         decreased the time it took to get a change into source
         control, through the build system, and into deployment
-        packages by 80%, greatly increasing our response time.</li>
+        packages by 80%, greatly increasing our response time.</em></li>
 
-        <li>Directory Versioning - this was a big deal that caused us
+        <li><em>Directory Versioning - this was a big deal that caused us
         to actually evaluate Clearcase at one point.  The CVS Attic
         was killing us in checkout time and build time with the
         velocity of change we were making to the source base.  When
@@ -272,35 +274,35 @@
         attic, effectively wiping out the history of our source base.
         With Subversion, we can remove something from the repository
         and not suffer performance penalties later (and still be able
-        to get the deleted contents back).</li>
+        to get the deleted contents back).</em></li>
 
-        <li>Simpler (and faster) branching - we no longer have a full
+        <li><em>Simpler (and faster) branching - we no longer have a full
         time FTE managing branches.  We are now cycling this activity
         through the group.  Each developer can perform this activity,
-        because it is now part of his daily work.</li>
+        because it is now part of his daily work.</em></li>
       </ol>
 
-      <p>As a manager, converting to Subversion was one of the best
+      <p><em>As a manager, converting to Subversion was one of the best
       decisions I have made thus far that had a such a direct and
-      highly visible impact on the productivity of my team.</p>
+      highly visible impact on the productivity of my team.</em></p>
 
-      <p>I hope this helps you make your case for Subversion.  My
+      <p><em>I hope this helps you make your case for Subversion.  My
       personal opinion is that no one should even consider CVS at this
       point in time.  Subversion is a great product and the support
       you get just on the mailing lists alone (from the development
-      team no less!) is second to none.</p></em>
+      team no less!) is second to none.</em></p>
     </li>
 
 
     <li>
     <strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=72348"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72348"
           >Ross Mark of Controlling Edge
           Inc</a></strong>
           <tt>(22&nbsp;July&nbsp;2004)</tt>
           <br/>
  
-    <em><p>For my own company Controlling Edge and at one of my
+    <p><em>For my own company Controlling Edge and at one of my
         customers S4 Technology (www.s4-technology.com) I have been
         running subversion since 0.17 and have never looked
         back. While there were a few issues initially we have never
@@ -319,22 +321,22 @@
         rsync. We don't have the memory for a full svn client nor the
         disk space for the working copy but one day we will write our
         own svn client that can just do the checkout without the need
-        for the wc support files or the memory overhead.</p>
+        for the wc support files or the memory overhead.</em></p>
 
-    <p>For the past 9 years I had been installing CVS at customer
+    <p><em>For the past 9 years I had been installing CVS at customer
     sites that required version control and wouldn't hesitate now to
-    recommend SVN instead.</p></em>
+    recommend SVN instead.</em></p>
     </li>
 
     <li>
     <strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=72339"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72339"
           >John Szakmeister
           </a></strong>
           <tt>(21&nbsp;July&nbsp;2004)</tt>
           <br/>
 
-    <em><p>I work for a government contracting facility.  We develop
+    <p><em>I work for a government contracting facility.  We develop
         everything from hardware, to full-fledged software
         applications, all of which supports mission-critical
         activities.  We're currently using it on one of our most
@@ -344,9 +346,9 @@
         features and upgrades.  Our small test projects would turn
         into fully-funded applications, and as such, we had to
         restructure them.  It was just too painful with CVS, and we
-        decided to look for something better.</p>
+        decided to look for something better.</em></p>
 
-    <p>We found Subversion when it was at version 0.17.  We started
+    <p><em>We found Subversion when it was at version 0.17.  We started
     with just a few developers using it, and then migrated our other
     developers over time.  I can say without question that it has been
     one of the best decisions that we've made.  Subversion works
@@ -360,64 +362,65 @@
     data, and our developers have found it to be a very intuitive
     tool.  Subversion has been rock-solid in our environment, and very
     much complements our software engineering practices.  I can't
-    speak highly enough of it.</p></em>
+    speak highly enough of it.</em></p>
     </li>
 
     <li>
     <strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=10651"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=10651"
           >Stuart Robertson of Absolute Systems,
           Inc</a></strong>
           <tt>(5&nbsp;May&nbsp;2004)</tt>
           <br/>
  
-      <em><p>I introduced SVN to Absolute Systems Inc.
+      <p><em>I introduced SVN to Absolute Systems Inc.
       (www.absolutesys.com) where I work about a year ago, and for
       about 8 months we ran internal SVN pilots, played around to gain
-      experience and trust, etc.</p>
+      experience and trust, etc.</em></p>
 
-      <p>In the last 4 months we have migrated all of our internal
+      <p><em>In the last 4 months we have migrated all of our internal
       product source repositories from Visual Source-Safe to SVN using
-      an internally-written VSS-to-SVN migration tool.</p>
+      an internally-written VSS-to-SVN migration tool.</em></p>
 
-      <p>Our largest SVN repository is now 3.7GB and currently has
+      <p><em>Our largest SVN repository is now 3.7GB and currently has
       68806 revisions. We are running SVN 1.0.1 + Apache 2.0.48 on
-      Linux. ...</p>
+      Linux. ...</em></p>
 
-      <p>SVN is a superb piece of work, and it is a *huge* step
+      <p><em>SVN is a superb piece of work, and it is a *huge* step
       forward from VSS.  To put things in perspective... previously we
       had 26 VSS databases for one product, primarily because of
       problems with VSS when the repositories grow large.  As you can
       imagine, trying to manage product releases across so many
-      repositories was really painful.<p>
+      repositories was really painful.</em></p>
 
-      <p>Now, with SVN, *all* of the artifacts for that same product are
+      <p><em>Now, with SVN, *all* of the artifacts for that same product are
       in a single repository, meaning that with a few cheap copy
       operations all of the sources that make up a given release can
-      be grouped together. ...</p></em>
+      be grouped together. ...</em></p>
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=6523"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=6523"
           >Gustavo Niemeyer of Conectiva Linux</a></strong>
           <tt>(25&nbsp;February&nbsp;2004)</tt>
           <br/>
 
-      <em><p>I'm sure you are aware about the fantastic product you
+      <p><em>I'm sure you are aware about the fantastic product you
       people have built, but I'd like to tell you a little story which
-      should give new users some comfort about it.
+      should give new users some comfort about it.</em></p>
 
-      <p>Here in Conectiva we used to maintain our packages in a file
+      <p><em>Here in Conectiva we used to maintain our packages in a file
       based system, storing the latest SRPM packages, and also some
       old versions in case something bad happened. For a long time we
       wanted to build some system which would make our life easier in
       the daily work, and at the same time would give us some
-      flexibility accessing historic information.</p>
+      flexibility accessing historic information.</em></p>
 
-      <p>Shortening the history a lot, 1 year and 6 months ago, the
-      first revision was committed into our repository:</p></em>
+      <p><em>Shortening the history a lot, 1 year and 6 months ago, the
+      first revision was committed into our repository:</em></p>
 
       <pre>
       % svn log https://svn.distro.conectiva/repos/cnc -r 1
@@ -426,29 +429,30 @@
       
       Created basic structure.
       ------------------------------------------------------------------------
-      </pre>
+</pre>
 
-      <em><p>Since then, 5 complete Conectiva Linux distributions were
+      <p><em>Since then, 5 complete Conectiva Linux distributions were
       committed into the repository, and every single update in the
       distribution is done using Subversion. We've already surpassed
       50000 revisions, in a 30GB repository. Even though we have had
       space, memory, and other kinds of problems around the
       repository, I'm proud to say we have never lost a single bit of
-      information since then.</p>
+      information since then.</em></p>
 
-      <p>Based on this, the least I could do is sending a big THANK
-      YOU for everyone involved in the project.</p></em>
+      <p><em>Based on this, the least I could do is sending a big THANK
+      YOU for everyone involved in the project.</em></p>
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=14575"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14575"
           >Mark Bohlman of Teledata Communications</a></strong>
           <tt>(21&nbsp;July&nbsp;2004)</tt>
           <br/>
 
-      <em><p>Teledata Communications has been using Subversion for
+      <p><em>Teledata Communications has been using Subversion for
       storing all of the source code on all our software products for
       the past year (since version 0.24).  I have been very happy with
       the overall results and they way that developer impacts are
@@ -458,122 +462,122 @@
       year to the move away from our prior system with locking (and
       the corresponding messages back and for to have something
       'unlocked').  We continued to expand the use of the product to
-      all groups in the company.</p>
+      all groups in the company.</em></p>
 
-      <p>Mark Bohlman<br/>
-         Software Development Manager</p></em>
+      <p><em>Mark Bohlman<br/>
+         Software Development Manager</em></p>
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a href="http://www.asttool.com/"
         >Assenmacher Specialty Tools</a> and
         <a href="http://www.gladesoft.com/">GladeSoft</a></strong> (from
         Mark Grosberg's <a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=14573"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14573"
     >post</a>)<br/>
     <tt>(21&nbsp;July&nbsp;2004)</tt>
     <br/>
-      <em><p>AST makes automotive scan tools.  We keep our source code
+      <p><em>AST makes automotive scan tools.  We keep our source code
       for both the embedded side and the Windows interface side under
       Subversion.  In addition we keep our (large) databases under
-      Subversion as well.</p></em>
+      Subversion as well.</em></p>
 
-      <em><p>GladeSoft sells an embedded webserver toolkit and
+      <p><em>GladeSoft sells an embedded webserver toolkit and
       application framework. Subversion stores all of our code and
       documentation.  In addition we store all of our business records
-      in Subversion; so I guess we can't pull an Enron as easily :-)
-      </p></em>
+      in Subversion; so I guess we can't pull an Enron as easily
+      :-)</em></p>
 
-      <em><p>Neither company has lost a single change with
+      <p><em>Neither company has lost a single change with
       Subversion. Both companies also have satellite workers who use
       SSL to access the source repositories.  Subversion
       administration is relatively straightforward provided you use
       Apache so there are no permission problems. At AST most of the
       server administration is done by one of the mechanics who has
-      other work to do.</p></em>
+      other work to do.</em></p>
 
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=14696"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14696"
           >Robert Zeh of Error Free Software</a></strong>
           <tt>(23&nbsp;July&nbsp;2004)</tt>
           <br/>
 
-    <em>
-    <p>I manage a 13 member application development group for a
+    <p><em>I manage a 13 member application development group for a
     trading firm.  There are about 9 other developers outside the
     group, and some others, so we have about 20 people using our
-    subversion repository.</p>
+    subversion repository.</em></p>
 
-    <p>For the past 10 years we used SCCS.  It was very frustrating
+    <p><em>For the past 10 years we used SCCS.  It was very frustrating
     --- files could not be renamed or moved, developers would forget
     about locks they had acquired, and remote development was next to
     impossible.  SCCS also made our limited Windows development
-    painful (we are a Unix shop).</p>
+    painful (we are a Unix shop).</em></p>
 
-    <p>Since we switched to subversion things have been much better.
+    <p><em>Since we switched to subversion things have been much better.
     Our entire history was transported into our Subversion repository,
     so none of our history was lost.  I wrote a Python script to
     transform it directly from SCCS to Subversion, and it was
-    painless.</p>
+    painless.</em></p>
 
-    <p>Conflicts have been very rare.  The ability to easily branch
+    <p><em>Conflicts have been very rare.  The ability to easily branch
     has been very useful; developers can make commits to branches
     without breaking other people's code.  It's easier to see what
     people are working on as the commits hit our internal commit
     mailing list.  Since we tag each release, we're able to determine
     which source code contributed to a release.  TortiseSVN makes
     Windows development easy (no more ftping files over, or trying to
-    build on a remotely mounted samba drive).</p>
+    build on a remotely mounted samba drive).</em></p>
 
-    <p>Robert Zeh<br/>
+    <p><em>Robert Zeh<br/>
        Manager, Application Development<br/>
-       Error Free Software</p>
-    </em>
+       Error Free Software</em></p>
 
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=14695"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14695"
           >Chris Wein of Mobilygen</a></strong>
           <tt>(23&nbsp;July&nbsp;2004)</tt>
           <br/>
 
-    <em>
-    <p>I also have had a very positive experience moving from CVS to
-    Subversion in a commercial setting.  We are a small-ish silicon
+    <p><em>I also have had a very positive experience moving from CVS
+    to Subversion in a commercial setting.  We are a small-ish silicon
     valley startup that used to have everything in CVS.  Shortly after
     I joined as s/w manager I switched the s/w team to SVN (0.37) with
     excellent results.  We have had zero loss of data, zero down time,
     with effective branching, easy repository restructuring and
     constant time tags as our big positives.  The entire company will
     be moving in the near-ish future based on our pilot.  And of
-    course the support from this list is fantastic.</p>
+    course the support from this list is fantastic.</em></p>
 
-    <p><font color="red">[Fair play dictates that we also include the
-    wish-list portion of Chris's testimonial...]</font></p>
+    <p><em><font color="red">[Fair play dictates that we also include
+    the wish-list portion of Chris's testimonial...]</font></em></p>
 
-    <p>As for my wishlist, it is short - completely seamless and
+    <p><em>As for my wishlist, it is short - completely seamless and
     foolproof tracking of merge history at the same level as the
     commercial tools.  I don't want to remember revision numbers, I
     just want to branch and merge with the tool remembering common
     base versions etc.  This is really the only thing I miss about
-    ClearCase.</p>
+    ClearCase.</em></p>
 
-    <p><font color="red">[We agree :-).  Better merge tracking is on
-    Subversion's long-term <a href="roadmap.html">roadmap</a>.]</font></p>
+    <p><em><font color="red">[We agree :-).  Better merge tracking is
+    on Subversion's long-term <a
+    href="roadmap.html">roadmap</a>.]</font></em></p>
 
-    </em>
-
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong>Testimonial from Martin Pittenauer of SubEthaEdit
         (<a href="http://www.codingmonkeys.de/subethaedit/"
@@ -583,34 +587,37 @@
     <br/>
     <tt>(2&nbsp;June&nbsp;2004)</tt>
     <br/>
-      <em><p>We are using Subversion since version 0.17 and it never
+      <p><em>We are using Subversion since version 0.17 and it never
       let us down.  On contrary it provided a much better experience
       than any versioning system we have used before, including CVS
       and perforce. With Apple adding support for .svn files within
       NIBs with Xcode 1.2 we are certain that subversion is the ideal
       versioning platform for modern software development on Mac OS
-      X.</p></em>
+      X.</em></p>
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
-    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=6781"
+    href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=6781"
     >Sebastien Cevey</a></strong>
     <tt>(28&nbsp;February&nbsp;2004)</tt>
     <br/>
 
-      <em><p>... I've been using Subversion for personal and team
+      <p><em>... I've been using Subversion for personal and team
       projects for a few years now.  I never regretted it, except for
-      the deep frustration I feel everytime I have to go back to CVS.</p>
+      the deep frustration I feel everytime I have to go back to
+      CVS.</em></p>
 
-      <p>I am glad to have introduced many people to this software,
+      <p><em>I am glad to have introduced many people to this software,
       through projects, talks or a course on versionning systems.  I
       haven't heard anybody disappointed by it, and this doesn't
-      surprise me. ...</p></em>
+      surprise me. ...</em></p>
     </li>
 
-    <br/>
+    </ul>
+    <ul>
 
     <li><strong><a
          href="http://www.osnews.com/comment.php?news_id=6783">Reader
@@ -630,8 +637,6 @@
           repository. Subversion it is!</em>
     </li>
 
-    <br/>
-
   </ul>
 
 </div>


