uuencoding is no longer required for submission of patches to the bug

tracker.

en_US.ISO8859-1/articles/contributing/article.xml

@@ -261,9 +261,8 @@
 	<emphasis>do not</emphasis> use cut-and-paste because
 	cut-and-paste turns tabs into spaces and makes them unusable.
 	When patches are a lot larger than 20KB, consider compressing
-	them (eg. with &man.gzip.1; or &man.bzip2.1;) and using
-	&man.uuencode.1; to include their compressed form in your
-	problem report.</para>
+	them (eg. with &man.gzip.1; or &man.bzip2.1;) prior to
+	uploading them.</para>
 
       <para>After filing a report, you should receive confirmation
 	along with a tracking number.  Keep this tracking number so
@@ -360,14 +359,10 @@
 	<literal>[PATCH]</literal> in the synopsis of the
 	report.</para>
 
-      <indexterm>
-	<primary><command>uuencode</command></primary>
-      </indexterm>
-
       <para>If you feel it appropriate (e.g. you have added, deleted,
 	or renamed files), bundle your changes into a
-	<command>tar</command> file and run the &man.uuencode.1;
-	program on it.  Archives created with &man.shar.1; are also
+	<command>tar</command> file.
+	Archives created with &man.shar.1; are also
 	welcome.</para>
 
       <para>If your change is of a potentially sensitive nature, such
@@ -391,7 +386,7 @@
       <para>In the case of a significant contribution of a large body
 	work, or the addition of an important new feature to FreeBSD,
 	it becomes almost always necessary to either send changes as
-	uuencoded tar files or upload them to a web or FTP site for
+	tar files or upload them to a web or FTP site for
 	other people to access.  If you do not have access to a web or
 	FTP site, ask on an appropriate FreeBSD mailing list for
 	someone to host the changes for you.</para>