Bug ID: JDK-8003228 (props) sun.jnu.encoding should be set to UTF-8 [macosx]

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 7	JDK 8
7u40Fixed	8Fixed

sun.jnu.encoding is the encoding used for encoding/decoding file paths and is defaulting to the value of file.encoding on Mac. It has been suggested that this should be changed to always be UTF-8. Before doing that we require some technical reference to ensure that this is the right thing to do.

verified in b85
12-04-2013
I have reproduced the problem described by the CAP member. However, the issue is with the "file.encoding" property, and this bug was meant only to cover "sun.jnu.encoding", which it has, so I'm closing this issue. I have filed a new issues to cover the problem of file.encoding when launching apps on Mac via double-clicked .jar (JDK-8011194) or via webstart (JDK-8011195).
01-04-2013
More information from CAP member - Running from the cmdline actually gives the system property "file.encoding" a working value of "UTF-8" and not "US_ASCII" as double clicking the jar file. to reproudce the problem, just make an executable jar file that prints the value of the system property "file.encoding". It should not be "US_ASCII" as that disables the use of accented characters in file names. jAlbum is developed by using Netbeans. jAlbum isn't launched via webstart.It can be workarounded by explicitly passing -Dfile.encoding=UTF-8 as a startup parameter, but it is still better if this bug is fixed instead (there may always be users who miss such startup parameters for instance)
01-04-2013
CAP member had tried on the latest JDK 8 build(b81), but the file.encoding was still set to US_ASCII, does not seem the problem had been fixed.
27-03-2013
CAP member had reported the same issue and would like the fix backported to 7u release as well.
14-03-2013
This technical Q&A from Apple: http://developer.apple.com/library/mac/#qa/qa1173/_index.html states: "The lowest levels of Mac OS X...treat file names as UTF-8 encoded Unicode strings."
29-11-2012
See thread at: http://mail.openjdk.java.net/pipermail/jdk8-dev/2012-November/001609.html The main thing we need is an authoritative reference that confirms that sun.jnu.encoding should be fixed as UTF-8 on Mac.
14-11-2012

Duplicate :	JDK-7187821 - Default encoding changed from 6u33 to 7u6 [macosx]
Duplicate :	JDK-8001070 - sun.jnu.encoding get incorrectly set to US-ASCII
Duplicate :	JDK-8013831 - non-ascii chars in file can not be read or displayed when doubleclick a jar file
Relates :	JDK-8006039 - test/tools/launcher/I18NJarTest.java fails on Mac w/ LANG=C, LC_ALL=C
Relates :	JDK-8072130 - java/lang/instrument/BootClassPath/BootClassPathTest.sh fails on Mac OSX
Relates :	JDK-8011194 - Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
Relates :	JDK-8005962 - TEST_BUG: java/util/Properties/MacJNUEncoding can fail in certain environments
Relates :	JDK-7050570 - (fs) FileSystemProvider fails to initializes if run with file.encoding set to Cp037
Relates :	JDK-7130915 - File.equals does not give expected results when path contains Non-English characters on Mac OS X
Relates :	JDK-8011195 - Apps launched via webstart have file.encoding value of US-ASCII on Mac OS X