Correct a minor spelling error

RT Developers
1

This patch corrects the misspelling of separate on the
Ticket/Create.html page.

spelling_error.txt (716 Bytes)

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

“Tammy Dugan” tdugan@progeny.com writes:

This patch corrects the misspelling of separate on the
Ticket/Create.html page.

Actually, this error occurs 42 times throughout the RT 3.0.9
distribution (including comments).

Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAQyvv8gM8+Mr5peERApvbAKCn+NhnIuGbtfZa58fjOQHdFlqmPwCgxyCl
91ArBtIY4XcVGNdgiJRlSdI=
=CywZ
-----END PGP SIGNATURE-----

3

I corrected this misspelling only in the code that the RT user sees. I
didn’t think it would be appropriate to submit a patch fixing spelling
errors in the code/comments since there are probably several misspellings in
the code/comments. If I am mistaken and the code/comments patch would be
appropriate, let me know and I will submit it.

				Tammy Dugan
4

I corrected this misspelling only in the code that the RT user sees. I
didn’t think it would be appropriate to submit a patch fixing spelling
errors in the code/comments since there are probably several
misspellings in
the code/comments. If I am mistaken and the code/comments patch would
be
appropriate, let me know and I will submit it.

So, with the following caveats, I’m perfectly happy to have
misspellings in the code and comments corrected:

  • Please don’t break an API by correcting a misspelling in a function
    name. (Correct it and insert a symbol table alias for the old name

  • Scrip is intentional :wink:

  • Requestor isn’t quite as common a spelling as requester, but it’s
    widely enough used both inside RT and out that I don’t want to change
    it.

  • If you want to submit a patch to remove “colorful” phrasing from
    comments, the new phrasing should capture the intent and feel of the
    previous phrasing :wink:

Thanks,

Jesse

5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

“Tammy Dugan” tdugan@progeny.com writes:

I corrected this misspelling only in the code that the RT user sees.
I didn’t think it would be appropriate to submit a patch fixing
spelling errors in the code/comments since there are probably
several misspellings in the code/comments. If I am mistaken and the
code/comments patch would be appropriate, let me know and I will
submit it.

My problem is not really with the code and comments. But your patch
only fixes one of the Mason components. There are errors in three:

    share/html/Search/Bulk.html
    share/html/Ticket/Create.html
    share/html/Ticket/Elements/EditLinks

Also, it only changes the text within the <&|/l&> tags and doesn’t fix
it in the I18N files (fine for us English-speaking folks).

Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFARPnO8gM8+Mr5peERAo4KAJ9llBJ2qfGv2f3bioEVdKkNCoouBwCglqix
LbnHRsL6hpXmtpaZk8MYDrw=
=ybHu
-----END PGP SIGNATURE-----