[Rt-commit] rt branch, 4.0/config-copyedit, created. rt-4.0.0rc5-13-gdd67b0c

Alex Vandiver alexmv at bestpractical.com
Wed Feb 23 17:10:47 EST 2011


The branch, 4.0/config-copyedit has been created
        at  dd67b0ce712704525dad9687a61b4e941569b53b (commit)

- Log -----------------------------------------------------------------
commit cdb5df1aac096f8de16feaf91538c3bedf627fdc
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:00:41 2010 -0500

    Spellcheck

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index cc69e23..03c902f 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -89,7 +89,7 @@ Set($MinimumPasswordLength , "5");
 =item C<$Timezone>
 
 C<$Timezone> is used to convert times entered by users into GMT and back again
-It should be set to a timezone recognized by your local unix box.
+It should be set to a timezone recognized by your server.
 
 =cut
 
@@ -168,7 +168,7 @@ Set($DatabaseRequireSSL , undef);
 
 =item C<$UseSQLForACLChecks>
 
-In RT for ages ACL are checked after search what in some situtations
+In RT for ages ACL are checked after search what in some situations
 result in empty search pages and wrong count of tickets.
 
 Set C<$UseSQLForACLChecks> to 1 to use SQL and get rid of these problems.
@@ -187,14 +187,14 @@ then links for first, next, previous and last ticket are shown in
 the menu.
 
 To build full map RT has to fetch full result set out of DB what can
-eat lots of resourses. Using this option it's possible to limit number
+eat lots of resources. Using this option it's possible to limit number
 of tickets fetched.
 
 Set C<$TicketsItemMapSize> to number of tickets you want RT to look
 at to build the map. If full result set is bigger than that number
 then there would be no 'last' link in the menu.
 
-Set this to zero to return back to old behaviour.
+Set this to zero to return back to old behavior.
 
 =cut
 
@@ -243,7 +243,7 @@ C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored
 in the database.
 
 For mysql and oracle, we set this size at 10 megabytes.
-If you're running a postgres version earlier than 7.1, you will need
+If you're running a Postgres version earlier than 7.1, you will need
 to drop this to 8192. (8k)
 
 =cut
@@ -302,9 +302,9 @@ Set($RTAddressRegexp , undef);
 
 RT provides functionality which allows the system to rewrite
 incoming email addresses.  In its simplest form,
-you can substitute the value in $<CanonicalizeEmailAddressReplace>
-for the value in $<CanonicalizeEmailAddressMatch>
-(These values are passed to the $<CanonicalizeEmailAddress> subroutine in
+you can substitute the value in C<CanonicalizeEmailAddressReplace>
+for the value in C<CanonicalizeEmailAddressMatch>
+(These values are passed to the C<CanonicalizeEmailAddress> subroutine in
  F<RT/User.pm>)
 
 By default, that routine performs a C<s/$Match/$Replace/gi> on any address
@@ -329,7 +329,7 @@ Set($CanonicalizeOnCreate, 0);
 
 If C<$ValidateUserEmailAddresses> is true, RT will refuse to create users with
 an invalid email address (as specified in RFC 2822) or with an email address
-made of multiple email adresses.
+made of multiple email addresses.
 
 =cut
 
@@ -337,7 +337,7 @@ Set($ValidateUserEmailAddresses, undef);
 
 =item C<@MailPlugins>
 
-C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
+C<@MailPlugins> is a list of authentication plugins for L<RT::Interface::Email>
 to use; see L<rt-mailgate>
 
 =cut
@@ -481,7 +481,7 @@ These options only take effect if C<$MailCommand> is 'sendmail' or
 
 C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
-These options are good for most sendmail wrappers and workalikes
+These options are good for most sendmail wrappers and work-a-likes.
 
 These arguments are good for sendmail brand sendmail 8 and newer
 C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
@@ -494,7 +494,7 @@ Set($SendmailArguments , "-oi -t");
 =item C<$SendmailBounceArguments>
 
 C<$SendmailBounceArguments> defines what flags to pass to C<$Sendmail>
-assuming RT needs to send an error (ie. bounce).
+assuming RT needs to send an error (i.e. bounce).
 
 =cut
 
@@ -626,7 +626,7 @@ Set($FriendlyToLineFormat, "\"%s of ". RT->Config->Get('rtname') ." Ticket #%s\"
 =item C<$NotifyActor>
 
 By default, RT doesn't notify the person who performs an update, as they
-already know what they've done. If you'd like to change this behaviour,
+already know what they've done. If you'd like to change this behavior,
 Set C<$NotifyActor> to 1
 
 =cut
@@ -646,11 +646,11 @@ Set($RecordOutgoingEmail, 1);
 
 VERP support (http://cr.yp.to/proto/verp.txt)
 
-uncomment the following two directives to generate envelope senders
+Uncomment the following two directives to generate envelope senders
 of the form C<${VERPPrefix}${originaladdress}@${VERPDomain}>
 (i.e. rt-jesse=fsck.com at rt.example.com ).
 
-This currently only works with sendmail and sendmailppie.
+This currently only works with sendmail and sendmailpipe.
 
 =cut
 
@@ -830,9 +830,9 @@ Set(@LogToSyslogConf, ());
 
 =item C<$StatementLog>,
 
-RT has rudimentary SQL statement logging support if you have
-DBIx-SearchBuilder 1.31_1 or higher; simply set C<$StatementLog> to be
-the level that you wish SQL statements to be logged at.
+RT has rudimentary SQL statement logging support; simply set
+C<$StatementLog> to be the level that you wish SQL statements to be
+logged at.
 
 =cut
 
@@ -930,7 +930,7 @@ Set( $AutocompleteOwners, 0 );
 
 =item C<$WebDomain>
 
-Domain name of the RT server, eg 'www.example.com'. It should not contain
+Domain name of the RT server, e.g. 'www.example.com'. It should not contain
 anything else, but server name.
 
 =cut
@@ -950,7 +950,7 @@ Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
 
 =item C<$WebPath>
 
-If you're putting the web ui somewhere other than at the root of
+If you're putting the web UI somewhere other than at the root of
 your server, you should set C<$WebPath> to the path you'll be 
 serving RT at.
 
@@ -964,13 +964,13 @@ Set($WebPath, "");
 
 =item C<$WebBaseURL>, C<$WebURL>
 
-Usually you don't want to set these options. The only obviouse reason is
-RT accessible via https protocol on non standard port, eg
+Usually you don't want to set these options. The only obvious reason is if
+RT is accessible via https protocol on a non standard port, e.g.
 'https://rt.example.com:9999'. In all other cases these options are computed
 using C<$WebDomain>, C<$WebPort> and C<$WebPath>.
 
-C<$WebBaseURL> is the scheme, server and port (eg 'http://rt.example.com')
-for constructing urls to the web UI. C<$WebBaseURL> doesn't need a trailing /.
+C<$WebBaseURL> is the scheme, server and port (e.g. 'http://rt.example.com')
+for constructing URLs to the web UI. C<$WebBaseURL> doesn't need a trailing /.
 
 C<$WebURL> is the C<$WebBaseURL>, C<$WebPath> and trailing /, for example:
 'http://www.example.com/rt/'.
@@ -1108,7 +1108,8 @@ Set($MessageBoxWrap, "SOFT");
 
 =item C<$MessageBoxRichText>
 
-Should "rich text" editing be enabled? This option lets your users send html email messages from the web interface.
+Should "rich text" editing be enabled? This option lets your users
+send HTML email messages from the web interface.
 
 =cut
 
@@ -1116,7 +1117,7 @@ Set($MessageBoxRichText, 1);
 
 =item C<$MessageBoxRichTextHeight>
 
-Height of RichText javascript enabled editing boxes (in pixels)
+Height of rich text JavaScript enabled editing boxes (in pixels)
 
 =cut
 
@@ -1152,7 +1153,7 @@ Set($WikiImplicitLinks, 0);
 =item C<$TrustHTMLAttachments>
 
 if C<TrustHTMLAttachments> is not defined, we will display them
-as text. This prevents malicious HTML and javascript from being
+as text. This prevents malicious HTML and JavaScript from being
 sent in a request (although there is probably more to it than that)
 
 =cut
@@ -1197,7 +1198,7 @@ machine generated? A true value will do so; setting this to '0'
 will cause no such messages to be redistributed.
 You can also use 'privileged' (the default), which will redistribute
 only to privileged users. This helps to protect against malformed
-bounces and loops caused by autocreated requestors with bogus addresses.
+bounces and loops caused by auto-created requestors with bogus addresses.
 
 =cut
 
@@ -1206,8 +1207,8 @@ Set($RedistributeAutoGeneratedMessages, 'privileged');
 =item C<$PreferRichText>
 
 If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
-messages in preference to their plaintext alternatives. RT "scrubs" the 
-html to show only a minimal subset of HTML to avoid possible contamination
+messages in preference to their plain-text alternatives. RT "scrubs" the 
+HTML to show only a minimal subset of HTML to avoid possible contamination
 by cross-site-scripting attacks.
 
 =cut
@@ -1228,7 +1229,7 @@ Set($WebExternalAuth, undef);
 If C<$WebExternalAuthContinuous> is defined, RT will check for the
 REMOTE_USER on each access.  If you would prefer this to only happen
 once (at initial login) set this to a false value.  The default setting
-will help ensure that if your external auth system deauthenticates a
+will help ensure that if your external authentication system deauthenticates a
 user, RT notices as soon as possible.
 
 =cut
@@ -1453,7 +1454,7 @@ Set($HomepageComponents, [qw(QuickCreate Quicksearch MyAdminQueues MySupportQueu
 
 C<@MasonParameters> is the list of parameters for the constructor of
 HTML::Mason's Apache or CGI Handler.  This is normally only useful
-for debugging, eg. profiling individual components with:
+for debugging, e.g. profiling individual components with:
 
     use MasonX::Profiler; # available on CPAN
     Set(@MasonParameters, (preamble => 'my $p = MasonX::Profiler->new($m, $r);'));
@@ -1692,7 +1693,7 @@ Specifies which fields of L<RT::User> to match against and how to match each
 field when autocompleting users.  Valid match methods are LIKE, STARTSWITH,
 ENDSWITH, =, and !=.
 
-Not all User fields are publically accessible and hence won't work for
+Not all User fields are publicly accessible and hence won't work for
 autocomplete unless you override their accessibility using a local overlay or a
 plugin.  Out of the box the following fields are public: Name, EmailAddress,
 RealName, NickName, and Organization.
@@ -1820,7 +1821,7 @@ Set($AmbiguousDayInFuture, 0);
 
 =head1 Approval Configuration
 
-Configration for the approvl system
+Configuration for the approval system
 
 =over 4
 
@@ -1988,7 +1989,7 @@ finally 'any to any'.
 
 If you don't define any rights or there is no match for a
 transition RT will use B<DeleteTicket> or B<ModifyTicket> as
-apropriate.
+appropriate.
 
 =head3 Labeling and defining actions
 
@@ -2191,7 +2192,7 @@ Set(@Plugins, ());
 
 =item C<@JSFiles>
 
-a list of js files to be included in head
+a list of JavaScript files to be included in head
 
 Example:
 

commit 9ff442451256bb2a472d741f6140e0b492143ba4
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:39:43 2010 -0500

    Document DatabaseRTHost

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 03c902f..590b77f 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -113,10 +113,11 @@ Set($DatabaseType , '@DB_TYPE@');
 
 =item C<$DatabaseHost>, C<$DatabaseRTHost>
 
-The domain name of your database server.
+The domain name of your database server.  If you're running mysql and
+on localhost, leave it blank for enhanced performance.
 
-If you're running mysql and it's on localhost,
-leave it blank for enhanced performance
+C<DatabaseRTHost> is the fully-qualified hostname of your RT server,
+for use in granting ACL rights on mysql.
 
 =cut
 

commit 662a52e3de90d28c596f06bd5e7de959ece5e42a
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:40:51 2010 -0500

    Copyedit a couple entries

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 590b77f..b46b627 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -169,13 +169,12 @@ Set($DatabaseRequireSSL , undef);
 
 =item C<$UseSQLForACLChecks>
 
-In RT for ages ACL are checked after search what in some situations
-result in empty search pages and wrong count of tickets.
+Historically, ACLs were checked on display, which could lead to empty
+search pages and wrong ticket counts.  Set C<$UseSQLForACLChecks> to 1
+to limit search results in SQL instead, which eliminates these problems.
 
-Set C<$UseSQLForACLChecks> to 1 to use SQL and get rid of these problems.
-
-However, this option is beta. In some cases it result in performance
-improvements, but some setups can not handle it.
+This option is still relatively new; it may result in performance
+problems in some cases, or significant speedups in others.
 
 =cut
 
@@ -183,19 +182,15 @@ Set($UseSQLForACLChecks, undef);
 
 =item C<$TicketsItemMapSize>
 
-In RT at display page of a ticket and there is the current search,
-then links for first, next, previous and last ticket are shown in
-the menu.
-
-To build full map RT has to fetch full result set out of DB what can
-eat lots of resources. Using this option it's possible to limit number
-of tickets fetched.
-
-Set C<$TicketsItemMapSize> to number of tickets you want RT to look
-at to build the map. If full result set is bigger than that number
-then there would be no 'last' link in the menu.
+On the display page of a ticket from search results, RT provides links
+to the first, next, previous and last ticket from the results.  In
+order to build these links, TY needs to fetch the full result set from
+the database, which can be resource-intensive.
 
-Set this to zero to return back to old behavior.
+Set C<$TicketsItemMapSize> to number of tickets you want RT to examine
+to build these links. If the full result set is larger than this
+number, RT will omitthe "last" link in the menu.  Set this to zero to
+always examine all results.
 
 =cut
 

commit 5e86692a85010afb247f3767b86b80c4ab31ab83
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:42:42 2010 -0500

    Minor copyediting

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index b46b627..e63c453 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -127,7 +127,8 @@ Set($DatabaseRTHost , '@DB_RT_HOST@');
 =item C<$DatabasePort>
 
 The port that your database server is running on.  Ignored unless it's
-a positive integer. It's usually safe to leave this blank
+a positive integer. It's usually safe to leave this blank; RT will
+choose the correct default.
 
 =cut
 
@@ -135,7 +136,7 @@ Set($DatabasePort , '@DB_PORT@');
 
 =item C<$DatabaseUser>
 
-The name of the database user (inside the database)
+The name of the user to connect to the database as.
 
 =cut
 
@@ -143,7 +144,7 @@ Set($DatabaseUser , '@DB_RT_USER@');
 
 =item C<$DatabasePassword>
 
-Password the C<$DatabaseUser> should use to access the database
+The password the C<$DatabaseUser> should use to access the database.
 
 =cut
 
@@ -161,7 +162,7 @@ Set($DatabaseName , '@DB_DATABASE@');
 =item C<$DatabaseRequireSSL>
 
 If you're using Postgres and have compiled in SSL support,
-set C<$DatabaseRequireSSL> to 1 to turn on SSL communication
+set C<$DatabaseRequireSSL> to 1 to turn on SSL communication.
 
 =cut
 
@@ -206,7 +207,7 @@ Set($TicketsItemMapSize, 1000);
 
 C<$OwnerEmail> is the address of a human who manages RT. RT will send
 errors generated by the mail gateway to this address.  This address
-should _not_ be an address that's managed by your RT instance.
+should I<not> be an address that's managed by your RT instance.
 
 =cut
 
@@ -215,7 +216,7 @@ Set($OwnerEmail , 'root');
 =item C<$LoopsToRTOwner>
 
 If C<$LoopsToRTOwner> is defined, RT will send mail that it believes
-might be a loop to C<$OwnerEmail>
+might be a loop to C<$OwnerEmail>.
 
 =cut
 
@@ -224,10 +225,8 @@ Set($LoopsToRTOwner , 1);
 =item C<$StoreLoops>
 
 If C<$StoreLoops> is defined, RT will record messages that it believes
-to be part of mail loops.
-
-As it does this, it will try to be careful not to send mail to the
-sender of these messages
+to be part of mail loops.  As it does this, it will try to be careful
+not to send mail to the sender of these messages.
 
 =cut
 
@@ -235,12 +234,12 @@ Set($StoreLoops , undef);
 
 =item C<$MaxAttachmentSize>
 
-C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored
-in the database.
+C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments
+stored in the database.
 
-For mysql and oracle, we set this size at 10 megabytes.
-If you're running a Postgres version earlier than 7.1, you will need
-to drop this to 8192. (8k)
+For mysql and oracle, we set this size to 10 megabytes.  If you're
+running a Postgres version earlier than 7.1, you will need to drop
+this to 8192. (8k)
 
 =cut
 
@@ -249,8 +248,8 @@ Set($MaxAttachmentSize , 10000000);
 
 =item C<$TruncateLongAttachments>
 
-C<$TruncateLongAttachments>: if this is set to a non-undef value,
-RT will truncate attachments longer than C<$MaxAttachmentSize>.
+If this is set to a non-undef value, RT will truncate attachments
+longer than C<$MaxAttachmentSize>.
 
 =cut
 
@@ -258,8 +257,8 @@ Set($TruncateLongAttachments , undef);
 
 =item C<$DropLongAttachments>
 
-C<$DropLongAttachments>: if this is set to a non-undef value,
-RT will silently drop attachments longer than C<MaxAttachmentSize>.
+If this is set to a non-undef value, RT will silently drop attachments
+longer than C<MaxAttachmentSize>.
 
 =cut
 
@@ -268,22 +267,24 @@ Set($DropLongAttachments , undef);
 =item C<$ParseNewMessageForTicketCcs>
 
 If C<$ParseNewMessageForTicketCcs> is true, RT will attempt to divine
-Ticket 'Cc' watchers from the To and Cc lines of incoming messages
-Be forewarned that if you have _any_ addresses which forward mail to
+Ticket 'Cc' watchers from the To and Cc lines of incoming messages.
+Be forewarned that if you have I<any> addresses which forward mail to
 RT automatically and you enable this option without modifying
-C<$RTAddressRegexp> below, you will get yourself into a heap of trouble.
+C<$RTAddressRegexp> below, you will get yourself into a heap of
+trouble.
 
 =cut
 
 Set($ParseNewMessageForTicketCcs , undef);
 
-=item C<$RTAddressRegexp> 
+=item C<$RTAddressRegexp>
 
-C<$RTAddressRegexp> is used to make sure RT doesn't add itself as a ticket CC if
-the setting above is enabled.  It is important that you set this to a 
-regular expression that matches all addresses used by your RT.  This lets RT
-avoid sending mail to itself.  It will also hide RT addresses from the list of 
-"One-time Cc" and Bcc lists on ticket reply.
+C<$RTAddressRegexp> is used to make sure RT doesn't add itself as a
+ticket CC if C<$ParseNewMessageForTicketCcs>, above, is enabled.  It
+is important that you set this to a regular expression that matches
+all addresses used by your RT.  This lets RT avoid sending mail to
+itself.  It will also hide RT addresses from the list of "One-time Cc"
+and Bcc lists on ticket reply.
 
 If you have a number of addresses configured in your RT database already, you
 can generate a naive first pass regexp by using
@@ -350,7 +351,7 @@ resolve arbitrary tickets!
 =item C<$ExtractSubjectTagMatch>, C<$ExtractSubjectTagNoMatch>
 
 The default "extract remote tracking tags" scrip settings; these
-detect when your RT is talking to another RT, and adjusts the
+detect when your RT is talking to another RT, and adjust the
 subject accordingly.
 
 =cut
@@ -479,7 +480,7 @@ C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
 These options are good for most sendmail wrappers and work-a-likes.
 
-These arguments are good for sendmail brand sendmail 8 and newer
+These arguments are good for sendmail brand sendmail 8 and newer:
 C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
 
 =cut
@@ -711,7 +712,7 @@ Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and
 signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
 
 If you want to allow people to encrypt attachments inside the DB then
-set C<AllowEncryptDataInDB> to true
+set C<AllowEncryptDataInDB> to true.
 
 Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
 emails encrypted for key RT doesn't have and can not decrypt.
@@ -846,7 +847,7 @@ This determines the default stylesheet the RT web interface will use.
 RT ships with several themes by default:
 
   web2            The default layout for RT 3.8
-  aileron         New default layout for RT 4.0
+  aileron         The default layout for RT 4.0
   ballard         Theme which doesn't rely on JavaScript for menuing
 
 This value actually specifies a directory in F<share/html/NoAuth/css/>
@@ -985,7 +986,7 @@ Set($WebURL, RT->Config->Get('WebBaseURL') . RT->Config->Get('WebPath') . "/");
 =item C<$WebImagesURL>
 
 C<$WebImagesURL> points to the base URL where RT can find its images.
-Define the directory name to be used for images in rt web
+Define the directory name to be used for images in RT web
 documents.
 
 =cut
@@ -1121,7 +1122,8 @@ Set($MessageBoxRichTextHeight, 200);
 
 =item C<$MessageBoxIncludeSignature>
 
-Should your user's signatures (from their Preferences page) be included in Comments and Replies
+Should your users' signatures (from their Preferences page) be
+included in Comments and Replies.
 
 =cut
 
@@ -1129,7 +1131,9 @@ Set($MessageBoxIncludeSignature, 1);
 
 =item C<$MessageBoxIncludeSignatureOnComment>
 
-Should your user's signatures (from their Preferences page) be included in Comments. Setting this to false overrides C<$MessageBoxIncludeSignature>.
+Should your users' signatures (from their Preferences page) be
+included in Comments. Setting this to false overrides
+C<$MessageBoxIncludeSignature>.
 
 =cut
 

commit ed6fc5df03bc44f3f2a886f48ff2e6c4535b733d
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:42:53 2010 -0500

    Fix a header to match the setting it is for

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index e63c453..81d70ec 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -312,7 +312,7 @@ passed to it.
 #Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$');
 #Set($CanonicalizeEmailAddressReplace , '@example.com');
 
-=item C<$CanonicalizeEmailAddressMatch>
+=item C<$CanonicalizeOnCreate>
 
 Set this to true and the create new user page will use the values that you
 enter in the form but use the function CanonicalizeUserInfo in

commit dd67b0ce712704525dad9687a61b4e941569b53b
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Dec 28 23:43:17 2010 -0500

    Trim trailing whitespace

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 81d70ec..7aeb081 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -474,7 +474,7 @@ These options only take effect if C<$MailCommand> is 'sendmail' or
 
 =over 4
 
-=item C<$SendmailArguments> 
+=item C<$SendmailArguments>
 
 C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
@@ -532,7 +532,7 @@ email's 'From'
 
 Set($SMTPFrom, undef);
 
-=item C<$SMTPDebug> 
+=item C<$SMTPDebug>
 
 C<$SMTPDebug> should be set to true to debug SMTP mail sending
 
@@ -633,7 +633,7 @@ Set($NotifyActor, 0);
 =item C<$RecordOutgoingEmail>
 
 By default, RT records each message it sends out to its own internal database.
-To change this behavior, set C<$RecordOutgoingEmail> to 0 
+To change this behavior, set C<$RecordOutgoingEmail> to 0
 
 =cut
 
@@ -787,8 +787,8 @@ Set($LogToScreen    , 'info');
 
 Logging to a standalone file is also possible, but note that the
 file should needs to both exist and be writable by all direct users
-of the RT API.  This generally include the web server, whoever
-rt-crontool runs as.  Note that as rt-mailgate and the RT CLI go
+of the RT API.  This generally includes the web server and whoever
+rt-crontool runs as.  Note that rt-mailgate and the RT CLI go
 through the webserver, so their users do not need to have write
 permissions to this file. If you expect to have multiple users of
 the direct API, Best Practical recommends using syslog instead of
@@ -862,8 +862,8 @@ Set($WebDefaultStylesheet, 'aileron');
 
 =item C<$UsernameFormat>
 
-This determines how user info is displayed. 'concise' will show one of 
-either NickName, RealName, Name or EmailAddress, depending on what exists 
+This determines how user info is displayed. 'concise' will show one of
+either NickName, RealName, Name or EmailAddress, depending on what exists
 and whether the user is privileged or not. 'verbose' will show RealName and
 EmailAddress.
 
@@ -948,7 +948,7 @@ Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
 =item C<$WebPath>
 
 If you're putting the web UI somewhere other than at the root of
-your server, you should set C<$WebPath> to the path you'll be 
+your server, you should set C<$WebPath> to the path you'll be
 serving RT at.
 
 C<$WebPath> requires a leading / but no trailing /, or it can be blank.
@@ -995,7 +995,7 @@ Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/");
 
 =item C<$LogoURL>
 
-C<$LogoURL> points to the URL of the RT logo displayed in the web UI
+C<$LogoURL> points to the URL of the RT logo displayed in the web UI.
 
 =cut
 
@@ -1207,7 +1207,7 @@ Set($RedistributeAutoGeneratedMessages, 'privileged');
 =item C<$PreferRichText>
 
 If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
-messages in preference to their plain-text alternatives. RT "scrubs" the 
+messages in preference to their plain-text alternatives. RT "scrubs" the
 HTML to show only a minimal subset of HTML to avoid possible contamination
 by cross-site-scripting attacks.
 
@@ -1266,7 +1266,7 @@ Set($WebExternalAuto , undef);
 =item C<$AutoCreate>
 
 If C<$WebExternalAuto> is true, C<$AutoCreate> will be passed to User's
-Create method.  Use it to set defaults, such as creating 
+Create method.  Use it to set defaults, such as creating
 Unprivileged users with C<{ Privileged => 0 }>
 ( Must be a hashref of arguments )
 
@@ -1287,9 +1287,9 @@ F<RT_SiteConfig.pm> will prevent session corruption.
 
 =item C<$AutoLogoff>
 
-By default, RT's user sessions persist until a user closes his or her 
-browser. With the C<$AutoLogoff> option you can setup session lifetime in 
-minutes. A user will be logged out if he or she doesn't send any requests 
+By default, RT's user sessions persist until a user closes his or her
+browser. With the C<$AutoLogoff> option you can setup session lifetime in
+minutes. A user will be logged out if he or she doesn't send any requests
 to RT for the defined time.
 
 =cut
@@ -1308,11 +1308,11 @@ Set($LogoutRefresh, 1);
 
 =item C<$WebSecureCookies>
 
-By default, RT's session cookie isn't marked as "secure" Some web browsers 
+By default, RT's session cookie isn't marked as "secure" Some web browsers
 will treat secure cookies more carefully than non-secure ones, being careful
-not to write them to disk, only send them over an SSL secured connection 
-and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value. 
-NOTE: You probably don't want to turn this on _unless_ users are only connecting
+not to write them to disk, only send them over an SSL secured connection
+and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value.
+NOTE: You probably don't want to turn this on I<unless> users are only connecting
 via SSL encrypted HTTP connections.
 
 =cut
@@ -1322,10 +1322,10 @@ Set($WebSecureCookies, 0);
 =item C<$WebFlushDbCacheEveryRequest>
 
 By default, RT clears its database cache after every page view.
-This ensures that you've always got the most current information 
+This ensures that you've always got the most current information
 when working in a multi-process (mod_perl or FastCGI) Environment
 Setting C<$WebFlushDbCacheEveryRequest> to '0' will turn this off,
-which will speed RT up a bit, at the expense of a tiny bit of data 
+which will speed RT up a bit, at the expense of a tiny bit of data
 accuracy.
 
 =cut
@@ -1419,7 +1419,7 @@ use a monospaced font, no matter what the value of C<$PlainTextMono> is.
 Set($PlainTextPre, 0);
 
 
-=item C<$PlainTextMono> 
+=item C<$PlainTextMono>
 
 To display plaintext attachments,
 Set C<$PlainTextMono> to 1 to use monospaced font and preserve
@@ -1473,11 +1473,11 @@ Set ($DefaultSearchResultFormat, qq{
    '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#',
    '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
    Status,
-   QueueName, 
-   OwnerName, 
-   Priority, 
+   QueueName,
+   OwnerName,
+   Priority,
    '__NEWLINE__',
-   '', 
+   '',
    '<small>__Requestors__</small>',
    '<small>__CreatedRelative__</small>',
    '<small>__ToldRelative__</small>',
@@ -1486,7 +1486,7 @@ Set ($DefaultSearchResultFormat, qq{
 
 =item C<$DefaultSelfServiceSearchResultFormat>
 
-C<$DefaultSelfServiceSearchResultFormat> is the default format of searches displayed in the 
+C<$DefaultSelfServiceSearchResultFormat> is the default format of searches displayed in the
 SelfService interface.
 
 =cut
@@ -1527,7 +1527,7 @@ Set(%AdminSearchResultFormat,
         .q{,'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
         .q{,__AppliedTo__, __FriendlyType__, __FriendlyPattern__},
 
-    Scrips => 
+    Scrips =>
         q{'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__id__</a>/TITLE:#'}
         .q{,'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__Description__</a>/TITLE:Description'}
         .q{,__Stage__, __Condition__, __Action__, __Template__},
@@ -1585,11 +1585,11 @@ Set($DontSearchFileAttachments, undef);
 
 =item C<%ChartFont>
 
-The L<GD> module (which RT uses for graphs) ships with a builtin font 
-that doesn't have full Unicode support. You can use a given TrueType font 
-for a specific language by setting %ChartFont to (language =E<gt> the 
+The L<GD> module (which RT uses for graphs) ships with a builtin font
+that doesn't have full Unicode support. You can use a given TrueType font
+for a specific language by setting %ChartFont to (language =E<gt> the
 absolute path of a font) pairs. Your GD library must have support for
-TrueType fonts to use this option. If there is no entry for a language 
+TrueType fonts to use this option. If there is no entry for a language
 in the hash then font with 'others' key is used.
 
 RT comes with two TrueType fonts covering most available languages.
@@ -2282,12 +2282,12 @@ Set($ShowRTPortal => 1);
 
 =item C<$DevelMode>
 
-RT comes with a "Development mode" setting. 
-This setting, as a convenience for developers, turns on 
-all sorts of development options that you most likely don't want in 
+RT comes with a "Development mode" setting.
+This setting, as a convenience for developers, turns on
+all sorts of development options that you most likely don't want in
 production:
 
-* Turns off Mason's 'static_source' directive. By default, you can't 
+* Turns off Mason's 'static_source' directive. By default, you can't
   edit RT's web ui components on the fly and have RT magically pick up
   your changes. (It's a big performance hit)
 
@@ -2302,9 +2302,9 @@ Set($DevelMode, '@RT_DEVEL_MODE@');
 
 What abstract base class should RT use for its records. You should never change this.
 
-Valid values are 
+Valid values are:
 
-=over 
+=over
 
 =item DBIx::SearchBuilder::Record
 

-----------------------------------------------------------------------


More information about the Rt-commit mailing list