Regen after r267848.

Sponsored by:	The FreeBSD Foundation
Update the vim editor config section, adding gjb's .vimrc.  Also add a
a post-processing step to avoid an embedded literal tab, and a short
note on usage.

PR:		191137
Submitted by:	venture37@geeklan.co.uk
Whitespace-only fixes, translators please ignore.
- Merge the following from the English version:

	r45093 -> r45107	head/ja_JP.eucJP/share/xml/news.xml
Remove obsolete example build instructions.  Update book and article
examples for DocBook 5 and FreeBSD DTD.

Note to translators: there are content whitespace changes in the example
programlistings that should be included in translations.
Whitespace-only fixes, translators please ignore.
Correct and expand DocBook examples, fix some that have embarrassing
errors and some that do exactly what the guidelines say to avoid.
Remove dash from example partition label and clarify wording.  A dash
can be used in a partition label, but not in a UFS label.  Even though
users are told not to use identical labels, we can remove one source
of potential confusion by sticking to the lowest common denominator.

Submitted by:	taras on IRC
Add xmj@'s consultancy Perceivon to the commercial Vendors section

PR:		191295
Submitted by:	xmj (modified)
Approved by:	bcr
Start building the 2009 press release page.  This was previously missing,
leading to a broken link at the bottom of
http://www.freebsd.org/news/press.html
Update the 9.3R schedule to reflect -RC2 builds started on time.

Approved by:	re (implicit)
Sponsored by:	The FreeBSD Foundation
add a new contributor Koichiro IWAO
o Document the current status of releng/9.3.
o The stable/9 branch is open again.
Add a link to the FreeBSD Journal.

Requested by:	anne, deb
Sponsored by:	The FreeBSD Foundation
Increment the layout.css date to try to prevent caching of the
old file.

Sponsored by:	The FreeBSD Foundation
Switch 9.3 to RC2.

Sponsored by:	The FreeBSD Foundation
Announce 9.3-RC2.

Approved by:	re (implicit)
Sponsored by:	The FreeBSD Foundation
The script in ~fenner relies on CVS.  I've modified it for svn.

In addition, call out that technical conversations should not happen in
private.
- Non-redistribution of content on the developers@ mailing list has
  little to do with copyright and more to do with ethics.

- Make it more clear what type of content is off-topic on developers@
Attempt to fix some can't-possibly-work perl.