| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2225744 | 7u6 | Chris Bensen | P2 | Closed | Fixed | b15 |
The string files in jdk7u-dev forest do not have UTF-16 BOM (byte order mark) in the beginning of the file:
deploy/src/plugin/macosx/controlpanel/prefpane/en.lproj/JavaControlPanel.strings
deploy/src/plugin/macosx/controlpanel/prefpane/en.lproj/InfoPlist.strings
WPTG now supports translation of .strings files, but the files were rejected due to missing BOM. I was able to manually convert the files to UTF-16 using
% iconv -f UTF-8 -t UTF-16 utf8_file > utf16_file
deploy/src/plugin/macosx/controlpanel/prefpane/en.lproj/JavaControlPanel.strings
deploy/src/plugin/macosx/controlpanel/prefpane/en.lproj/InfoPlist.strings
WPTG now supports translation of .strings files, but the files were rejected due to missing BOM. I was able to manually convert the files to UTF-16 using
% iconv -f UTF-8 -t UTF-16 utf8_file > utf16_file
- backported by
-
JDK-2225744 [macosx] NLS: .strings files do not have UTF-16 BOM
-
- Closed
-