This is not only for code consistency, but also for consistency of
output.  Encode::encode_utf8(...) is equivalent to
Encode::encode("utf8",...) which is the non-"strict" form of UTF-8.
Strict UTF-8 encoding differs in that (from `perldoc Encode`):

    ...its range is much narrower (0 ..  0x10_FFFF to cover only 21 bits
    instead of 32 or 64 bits) and some sequences are not allowed, like
    those used in surrogate pairs, the 31 non-character code points
    0xFDD0 .. 0xFDEF, the last two code points in any plane (0xXX_FFFE
    and 0xXX_FFFF), all non-shortest encodings, etc.

RT deals with interchange with databases, email, and other systems.  In
dealing with encodings, it should ensure that it does not produce byte
sequences that are invalid according to official Unicode standards.

Replace newlines with spaces, to prevent content wrapped across lines
from running together when exported as TSV.

This prevents the web display parts of column map from leaking into the
spreadsheet, such as through custom fields.  However, multiple value CFs
are now output all run together instead of separated by "<br>" elements.
Whether this is an improvement or not depends on your point of view, but
it will be remedied to something saner in a following commit.

Any HTML entities are also decoded so that no HTML should be left.

If # is the first column (as usual), then the header will be output as a
"comment" and the columns will be off by one.  Catch and fix the most
common failure mode.

This updates our copyright to 2011, rewrites the email address and
strips a lot of extra whitespace.  These license blocks should now be
identical to 4.0-trunk which will help significantly with merges.

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/3.8/trunk@18354 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/3.8/branches/3.8.2-releng@17585 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/3.8/trunk@17581 e417ac7c-1bcc-0310-8ffa-8f5827389a85

RT-Status: resolved

Display times in the user's timezone.  This is a horrible, horrible
   hack, but it's no worse than the other horrors in the file already.
   ====> This breaks backwards compatibility! <====

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/3.8/trunk@13732 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.8-TESTING@13102 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.8-TESTING@13003 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.8-TESTING@12308 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-RTIR-RELENG@11689 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.6-RELEASE@11686 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL@10957 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL-RTIR-2.2@7941 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL-RTIR-2.0@7940 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL-RTIR-2.0@7939 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL-RTIR-2.2@7909 e417ac7c-1bcc-0310-8ffa-8f5827389a85

git-svn-id: svn+ssh://svn.bestpractical.com/svn/bps-public/rt/branches/3.7-EXPERIMENTAL@7674 e417ac7c-1bcc-0310-8ffa-8f5827389a85