file.encoding vs. sun.jnu.encoding(?) on OS X (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Thu Nov 22 13:45:00 PST 2012
- Previous message: file.encoding vs. sun.jnu.encoding(?) on OS X
- Next message: file.encoding vs. sun.jnu.encoding(?) on OS X
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 22/11/2012 20:10, Paul Taylor wrote:
:
Just tried the latest ea release macbook:songkong paul$ java -version java version "1.7.012-ea" Java(TM) SE Runtime Environment (build 1.7.012-ea-b02) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b25, mixed mode)
and Im still getting a problem that files containing certain chars are not failing file.exists(); Is this the issue discussed that is meant to be fixed in 7u12 ? 7130915 is fixed in 7u12, 8003228 is not. As I said in the previous mail, I think these issues have been mixed up (for understandable reasons).
For 8003228 then we need to get an authoritative reference before fixing the value of sun.jnu.encoding to UTF-8. Scott may be able to provide this. In the mean-time then setting your locale appropriately is the workaround.
:
Also do you have an eta for when 7u10 final , and 7u12 final will be available ?
I just checked the 7u12 page [1] and it doesn't look like a GA date has been published yet.
-Alan
[1] http://openjdk.java.net/projects/jdk7u/releases/7u12.html
- Previous message: file.encoding vs. sun.jnu.encoding(?) on OS X
- Next message: file.encoding vs. sun.jnu.encoding(?) on OS X
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]