JDK-6966402 : Request to localise two strings in deployment code
  • Type: Bug
  • Component: globalization
  • Sub-Component: translation
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-07-02
  • Updated: 2010-12-04
  • Resolved: 2010-07-26
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 6 JDK 7
6u21-rev b08Fixed 7Fixed
Related Reports
Relates :  
Description
I need two strings translated in our JRE code to make an error message more clear.

The lines are :
http://opengrok.ireland:8080/source/xref/6-rev-latest/deploy/src/javaws/share/native/messages.properties#10
http://opengrok.ireland:8080/source/xref/6-rev-latest/deploy/src/javaws/share/native/messages.properties#11

error.badinst.execv=Bad installation. Error invoking Java VM (execv)
error.badinst.sysexec=Bad installation. Error invoking Java VM (SysExec)

Property files are at : http://opengrok.ireland:8080/source/xref/6-rev-latest/deploy/src/javaws/share/native/
My ws is at /net/v245-sus.ireland/suspool/home/sean/6-rev-latest/deploy in case someone needs an NFS copy.

I need them translated to the following :

error.badinst.execv=Error encountered while invoking Java Web Start (execv)
error.badinst.sysexec=Error encountered while invoking Java Web Start (SysExec)

Comments
EVALUATION Our default localization process is that we will integrate the l10n resource files in the next build after English resource change is integrated. We need the test case (steps) that we can use to verify our message change in our internal build and the PIT build. Since 6898437 is going to be integrated in 6u23. If the CR fix can be integrated in 6u23 b01, we will be able to integrate l10n change in 6u23 b02. According to Michael, the change is urgent. If Sean likes, I could deliver the translated resource files to him directly by email, and he will handle the integration work. In this way, we also need to verify the l10n changes on his own build and the PIT build. Sean, please let me know which approach do you prefer.
05-07-2010