-
Bug
-
Resolution: Fixed
-
P3
-
6u51, 7u4, 7u40, 8
-
b103
-
os_x
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8033212 | 7u80 | Brent Christian | P3 | Resolved | Fixed | b01 |
JDK-8060941 | 7u79 | Brent Christian | P3 | Resolved | Fixed | b01 |
JDK-8057412 | 7u76 | Brent Christian | P3 | Resolved | Fixed | b01 |
JDK-8035590 | 7u65 | Brent Christian | P3 | Resolved | Fixed | b01 |
JDK-8026230 | 7u60 | Brent Christian | P3 | Closed | Fixed | b07 |
The problem remains that once the file is loaded, non-ASCII characters *contained* in files do not display correctly. This is due to the "file.encoding" property being set to US-ASCII for apps launched by double-clicking a .jar file.
- backported by
-
JDK-8033212 Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
- Resolved
-
JDK-8035590 Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
- Resolved
-
JDK-8057412 Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
- Resolved
-
JDK-8060941 Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
- Resolved
-
JDK-8026230 Apps launched via double-clicked .jars have file.encoding value of US-ASCII on Mac OS X
- Closed
- relates to
-
JDK-7193966 [macosx] [regresison from Apple's Java 6] non-ascii chars can not be read or displayed, causing files to not load, files not found
- Closed
-
JDK-8072130 java/lang/instrument/BootClassPath/BootClassPathTest.sh fails on Mac OSX
- Resolved
-
JDK-8003228 (props) sun.jnu.encoding should be set to UTF-8 [macosx]
- Closed
-
JDK-8011195 Apps launched via webstart have file.encoding value of US-ASCII on Mac OS X
- Closed
-
JDK-8013831 non-ascii chars in file can not be read or displayed when doubleclick a jar file
- Closed