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.
Policytool will be rewritten in swing. Although there are no new messages, mnemonics are added to all menu items and most buttons. There are also three keyboard shortcuts in the File menu (New, Open, Save).
Comments
verified in b122:
http://bej301328.cn.oracle.com/gatejava/test/jdk2/results/8/b122/jre-x86-policytool.html
07-01-2014
Michael, can you give some explanation to the screen shots page? All rows are labeled "fail" but at least I cannot find out what's wrong with the first screen shot of the zh_CN row.
04-12-2013
You are right, there is Resources_zh_HK.java in the same directory. I need to try to look for old history about that file (might be related to JDK-4463546). If the file is needed, we need to copy the content of zh_TW file to it. zh_HK just uses the same translation as zh_TW.
27-11-2013
We do not translate into zh_HK.
27-11-2013
Thanks a lot Leif.
27-11-2013
this task will be taken care of by JDK-8026741
23-10-2013
This is part of message drop50 work.
23-10-2013
If an European locale could have different shortcut keys, it seems they should be in a translatable resource file. Is there a label that we can put into the resource file to inform the translator not to translate something?
18-10-2013
If you compare with other editors that ship with the operating systems, like WordPad, I think they usually do not change these common shortcuts in other locales.
They can be changed if necessary, though, as long as they follow the syntax for KeyStroke.getKeyStroke(String). See http://docs.oracle.com/javase/7/docs/api/javax/swing/KeyStroke.html#getKeyStroke%28java.lang.String%29.
When running on MacOS, if the accelerator is given as "control X" where X is a single character, then the app will replace that with "meta X". So it is best to keep that form.
18-10-2013
I think they should not be touched. The code compares the value with "control" and do something special.
18-10-2013
I was wondering what the translators need to do for "control N", "control O", and "control S"?
+ {"New", "&New"},
+ {"New.accelerator", "control N"},
+ {"Open", "&Open..."},
+ {"Open.accelerator", "control O"},
+ {"Save", "&Save"},
+ {"Save.accelerator", "control S"},
+ {"Save.As", "Save &As..."},