The forum list now highlights forums containing topics with recent
replies even if sticky items are present. The topic updated date is
used for this too, to avoid having to make further changes to the
way that the forum change date was propagated. It's "more correct"
this way anyway.

Gave up trying to figure out what was wrong with the YAML
syntax colouring engine this time and just wrote it off as
a bad job - the whole thing is commented out. It's not as
if many people browse the SVN tree anyway! We can most
definitely live without it.

Add ROOL site-specific links to CMS and forum pages in the
list and details views for bounties. Make the title of a
bounty in the list view a link to the 'show' page too.

Under certain conditions the YAML syntax parser could get caught in a
tight loop. This was causing the bug tracker Ruby process to crash if
client browsers visited particular YAML files in the Subversion tree.

For some reason, the RCVSWeb default layout was claiming that the page was
in German in the HTML tag.

Sort out the Instiki default layout's handling of titles, which
was a bit of a mess and looks like it's not been historically
properly maintained across Instiki versions and Rails releases
(e.g. the use of "@action_name", rather than "action_name()").
The current document's heading - Home Page aside - is shown as
the main title now. Existing pages with their own duplicate
titles inline will need amending.

Remove most of the Instiki styles related to tables in the content area,
now that the global stylesheet takes care of this. Use of Textile such as:

table(bordered).
| cell | cell | cell | (etc.)

...will give bordered tables as before, else tables have no borders. This
seems to look best on average.

Don't let images make the body column too wide; scale them instead.

Increase hub idle timeout to 4 hours.

Ticket #276 asks for the forum description to be included in the detail
view for a topic, listing posts. The list of topics within a forum sets
a precedent by putting this information in the sidebar, so I've copied
that mechanism for the posts index view.

Add "|" as another character which is interpreted as a closure to a named
reference syntax Textile tag. Without this, the Textile link corrector can
trip up in tables unless the author puts a space before the "|" separating
one cell from another immediately after a named reference syntax link:

|"This would fail":failure|Another cell|

[failure]http://www.test.com/

Further nasty regular expression work, to patch up diff output so that it
doesn't try to self-close DIV tags. Since the system works internally with
XHTML but pages are served as if HTML to prevent browsers choking on the
unusual data type, self-closing elements are ignored - esentially the
browser views the "/>" closing the tag as a small syntax error. With DIVs,
this can lead to big problems when diffs are viewed; the diff engine
canonicalises empty DIV containers, such as those used for automatic tables
of contents and turns them into self-closing elements, which browsers then
think are still *open* when rendering the page. The result is a bit of a
mess. Anyway, replacing self-closing DIVs with normal HTML container style
syntax works around the issue.

Tagging after 2011-03-14 upgrade.

Adding directory to take pseudo-tag for overall site after
2011-03-14 upgrade.

Tagging after 2011-03-14 upgrade.