ballard has its own msie6.css
css fixes for ie6

the main concern here is to make RT work and not so ugly on ie6.
most changes are plain position fixes, but here is the weird one:

though we hide ".message-stanza.closed" in history-folding.css,
ie6 hides "Show quoted text" span too, which is actually
".message-stanza-folder.closed", so I had to force the display
in msie6.css like:

    span.message-stanza-folder {
        display: inline !important;
    }
css fix to make extra buttons visible on ie6

this includes "Clear All", "Check All" buttons in /Search/Bulk.html
Advise about GPG configuration in GPG error message

When logging error messages from GPG, also provide a pointer to
RT_Config.pm to help the user configure or disable GPG support.
Add eval to trap fatal on scrip condition lookup when the condition id is 0.
Liberally handle email addresses surrounded by single quotes in incoming headers

Outlook is known to produce mail headers like so:

    Cc: "John Smith" <'jsmith@example.com'>

While Mr. Smith won't have received the original mail Cc'd to him and
RT, RT can at least notify him of future mail on the ticket if
$ParseNewMessageForTicketCcs is enabled.

This commit handles incoming mail.  There are still many places that
directly parse mail headers from the database and don't strip
surrounding single quotes.  For example, headers like the above will
still produce incorrect suggestions for the "One-time Cc/Bcc" fields on
ticket reply/comment pages.  To fix this for good, we need to first
consolidate all email address/header parsing into RT::EmailParser and
then fix the problem in a single place.
text/plain can also contain invalid utf8 data

so don't test mimetype, but check if it's pure ascii instead

see issue #20191
keep cf select values as an arrayref if there are multiple values in ticket clone

otherwise those values won't be able to cloned correctly.

btw the ticket clone code is used when creating a new link ticket on ticket
display page.

see also #20400
Remove the local-install Makefile target

The local-install target was added in 578192f, but there was never a
shipped set of local/{etc,html,po} directories to install from (as far
back as we can reasonably go in svn history).  Thus the target always
errored out, although the errors were intentionally ignored.  Creation
of the local/ hierarchy in /opt/rt4 is handled by the "dirs" target.

The best guess is that this supported bundling of customizations when
building custom tarballs.  These days we have installable extensions.
show queue id for default queue if current user lacks SeeQueue right

it's rare but valid that a user can create/edit tickets in a queue but doesn't
have SeeQueue right.

in that rare case, tickets could be moved to another queue accidently in edit
page, see also #19224
Add docs for rt-crontool
LinkType = <id> search was switched from LocalX to X columns

It was side effect of 5075951855fe6bfb4f3698386a1a3d4827f25259
change.
The AdminSearchResultFormat for CustomFields used can()

Since our ::Records are made of AUTOLOAD, can() fails until someone
calls ->Name on a Queue.  /Admin/CustomFields/ would show Applied #3
sometimes for a Queue until every rt-server process had called
$queue->Name.

RT has had a way to work around this forever, and now that 4.0-trunk
actually calls all _BuildAccessible on all our classes, we should just
use _Accessible.
make messagebox's width css(100%) cover paddings and borders too

or the box will overflow a bit because of extra padding and border widths
Wording changes
Make CKeditor work with the back button

Using the back button caused the html-filled output of the submission
to appear in the textarea, then be encoded _again_ by the
ckeditor-creation code.  We work around this by inserting a
<input type="text" style="display:none"> element into the form, which
we update when we upgrade the field.  This serves dual purposes: it
notifies the perl side of the content type of the field, but it also
serves as a storage of if the text->html encoding has already happened
in javascript.

This needs to be a type="text" because, unlike text="hidden", values
in those fields are restored to their submit-time values when the back
button is pressed.  Thus, the only way to back this system safe from
the back button is to store that information in a non-hidden text
area, and hide it using CSS.
Update RT::Template->Create to return failure message if requested when called.
Fix tab weirdness
Merge branch '4.0/return-errors-on-template-create' into 4.0-trunk
set transfer encoding to base64 for dashboard html email

there is line length limit for messages in rfc 2822(section 2.1.1).
though some email systems can auto-wrap long lines perfectly, some did it poorly.
dashboard html can have very long lines(1000+ chars, e.g. when there are links
to customized searches with long queries), setting to base64 here is to make sure
it won't be cut off by buggy email systems.