Re: Why did Java change Japanese native encoding in Leopard? (Radar #5015600)

• Subject: Re: Why did Java change Japanese native encoding in Leopard? (Radar #5015600)
• From: Andre-John Mas <email@hidden>
• Date: Fri, 29 Feb 2008 09:04:20 -0500
• Delivered-to: email@hidden
• Delivered-to: email@hidden

On 29-Feb-08, at 02:18 , Pratik Solanki wrote:

On Feb 28, 2008, at 4:56 PM, Michael Good wrote:

Hi Pratik,

Thanks again for your suggestion of using  -Dfile.encoding=Shift_JIS
when we start Java via JNI Invocation. Our initial testing indicates
that this does indeed fix the problem. I am still hoping that this
system property is indeed documented somewhere that I have missed.

I looked at the javadoc for System.getProperties() <http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#getProperties() > expecting to find it there but didn't. So, as Adrian points out this is not a mandated property. However, I think it is quite safe to use it. The property has been around for a long time and I think its become more like a de-facto standard. Certainly on Mac OSX, all versions of java honour it.

Andre
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

• Prev by Date: Re: Class.forName(..) throws exception in Java 5 applet--okay when run as Java 6 applet or Java 5/6 application
• Next by Date: Re: Class.forName(..) throws exception in Java 5 applet--okay when run as Java 6 applet or Java 5/6 application
• Previous by thread: Re: Why did Java change Japanese native encoding in Leopard? (Radar #5015600)
• Next by thread: Re: Why did Java change Japanese native encoding in Leopard? (Radar #5015600)
• Index(es):
  • Date
  • Thread