JDK install corrupts /etc/mailcap during installation

FULL PRODUCT VERSION :
java version "1.6.0_22"
Java (TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Linux <hostname> 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:43 EDT 2010 i686 i686 i386 GNU/Linux

EXTRA RELEVANT SYSTEM CONFIGURATION :
Standard installation of Red Hat Linux and standard installation of JDK RPM

A DESCRIPTION OF THE PROBLEM :
Installation of jdk-1.6.0_22-fcs on Redhat Linux 5.5 consistently adds an invalid entry to /etc/mailcap.

The last line of the file prior to installation was:
 
application/msword; ooffice
 
and after installation of JDK it is:
 
application/msword; ooffice\napplication/x-java-jnlp-file; /usr/bin/javaws %s

(Note the invalid \n between office and application)
This occured with builds 20 and 21 of the jdk as well.



STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Standard Installation of Red Hat Linux 5
Standard installation of JDK 1.6.0 Update 22 RPM

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The installation should not be adding invalid \n in the /etc/mailcap file.
ACTUAL -
The installation adds an invalid \n in the /etc/mailcap file.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Workaround is to manually edit the /etc/mailcap file and remove the \n character.
I am ok deferring this, unix is a third class citizen and we don't approach it seriously enough, however this is not a new bug and customers know how to handle it. We really need to fix this in the next release however.