UTF-8 filename fix in jdk8 b73 - sun.jnu.encoding set to UTF-8 on Mac by 8003228 (was Re: File.exists() does not work on mac for non-English characters on Java 7 on Mac)
Steve Hannah
steve at weblite.ca
Wed Jan 23 10:53:14 PST 2013
I replied to the original thread, but I'll mention it here too. I
tried b73 and it seems to handle unicode characters in file names
correctly now, without requiring any workarounds.
-Steve
On Wed, Jan 23, 2013 at 10:27 AM, Brent Christian
<brent.christian at oracle.com> wrote:
> Alan pretty much said it.
>
> We have a fix in b73 of jdk8 that we're hoping will solve a lot of the
> remaining problems that people have seen in this area.
>
> If we hear that people are having success with b73, that will make a strong
> case for backporting this fix into a jdk7 update.
>
> So if you're in a position to give b73 a try, that would be a big help.
>
> Thanks,
> -Brent
>
> On 1/23/13 1:05 AM, Alan Bateman wrote:
>>
>> On 22/01/2013 21:41, Steve Hannah wrote:
>>>
>>> I just wanted to post my experiences with this bug. I was having
>>> trouble on OS X in both 1.7.0u11 and 1.7.0u12 with Japanese file names
>>> (File.exists() erroneously returning false).
>>>
>> Can you try jdk8-b73 in your environment without the app bundle change
>> and see if you still have an issue? Brent pushed a change to b73 that
>> defaults the value of sun.jnu.encoding to UTF-8 on Mac and we think this
>> should the issues that several folks on this list have reported. There
>> are several other changes in this general area so rnning with the latest
>> jdk8 build means a build with all the changes. I know Brent is planning
>> on getting wider feedback from folks that are willing to try out jdk8
>> builds. We need this before backports to jdk7u can be considered.
--
Steve Hannah
Web Lite Solutions Corp.
More information about the macosx-port-dev
mailing list