Hi Jarek, seems nobody gets interested at once... :)
What I could propose is: - submit an official bug record and mention that a patch is available; - wait for a while; - if no response again - try contacting one of the latest CVS committers directly. In my case that was Myriam Midi. Regards, Sergey Ushakov P.S. You are right, the idea of using Properties was not too bright... ----- Original Message ----- From: "Jaroslaw Lewandowski" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 14, 2002 11:51 AM Subject: Encodings.java patch > Hello, > > I'm currently developing application which uses Xalan XSLT processor. I > found that serializations in my character set (iso-8859-2) does not work > properly. After some testing, I found that problem is in > org.apache.xalan.serialize.Encodings class. This class uses > java.util.Properites class to read EncodingInfo values from > Encodings.properites resource. It uses as key mime-name of encoding, > unfortunately one mime-name has many java-names, but in Properties class > only the last one is active. > I decided to fix it, so there is patch for Encodings.java (rev. 1.11) and > this file itself. It uses stream to read values from property file, and > java.util.Vector to store it. > > Best regards > Jarek Lewandowski > [EMAIL PROTECTED] > > >
