JDK-7171668 : [macosx] NLS: .strings files do not have UTF-16 BOM
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7u6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: os_x
  • CPU: x86
  • Submitted: 2012-05-24
  • Updated: 2013-07-01
  • Resolved: 2012-06-20
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
7u6Fixed 8 b44Fixed
Description
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

Comments
Refer to JDK-8014937.
2013-07-01

EVALUATION The correct files have been attached. Currently, these files are blocking our automated translation drop system. We need these delivered to jdk8 and jdk7u6 as soon as possible. Thanks!
2012-06-13