Version Control With Subversion Source

Merge from ^/trunk/en r4386 (HTML stylesheet changes).

Merge from ^/trunk/en r4387 (moderize the '... Right Tool?' section).

Finish issue 65 ("Please talk about the cases where a true DVCS like
Git would be better than SVN") to the degree that I plan to do so.

* en/book/ch00-preface.xml
(svn.intro.righttool): Rework this section to make a distinction
between "choosing version control" and "choosing Subversion", and
then try to make an honest attempt to quickly explain how
Subversion differs from the DVCS tools and why one might (or might
not) choose it over such a tool.

* en/book/styles.css
Add custom styles for <sup> tags (so that don't bust through the top
of the line boundary) and mess up line spacing. Also, increase the
line height a bit to give lines of text a bit of breathing room.

Merge from ^/trunk/en r4384 (note 'format' and 'db/format' distinction).

* en/book/ch05-repository-admin.xml
(svn.reposadmin.basics): Convert descriptions of repository
directory members into full sentences, and add a warning about not
confusing REPOS/format with REPOS/db/format.

Suggested (at least in part) by: danielsh

Merge r4382 from ^/trunk/en (binary files and 'svn diff/annotate').

Finish issue 183 ("Document behaviour of 'svn diff' and 'svn blame'
with binary mime-types").

* en/book/ch03-advanced-topics.xml
(svn.advanced.props.special.mime-type): Mention the effect of a
binary MIME type property on diff and annotate commands.

Merge r4380 from ^/trunk/en (new 'svn annotate' section, et al).

Add a section about 'svn annotate' to the book. As requested in issue
183, point out that 'svn annotate' really wants to operate on
human-readable files only (but that --force will do its thang if
required).

* en/book/ch02-basic-usage.xml
(svn.tour.history): Mention 'svn annotate', too.
(svn.tour.history.browsing.annotate): New section.
(svn.tour.history.browsing.cat, svn.tour.history.browsing.list):
Give these sections meaningful, prose-y titles.