This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
If the labels described below are java programmatic variables or names, or come from a non FFJ jar file or from jdk itself, please close this bug or parts of it. And if they do, should they also come from a Bundle.properties file, so that they can be localized ? If so, please let me know and I can file RFE. A. Running in ja locale with pseudo localized FFJ, where each applicable string in Bundle.properties pseudo translated and Bundle files named Bundle_ja.properties are put in each <modulename>_ja.jar file in the locale subdir of where module lives. 1. Choose the color/font editor options->print settings->java editor 2. Click on Fonts and Colors to bring up Fonts and Colors Property editor 3. Click on the three dots in foreground color to invoke Color property editor 4. Under AWT pallette, the names of the colors do not appear to be from a Bundle.properties file. 5. Under System pallette, the words do not appear to be from a Bundle.properties file 6. Under Swing pallette, the words look to be names of java variables, but don't know if these should come from properties files or not. 7. The lower part of the window does have Japanese in it, so assume this is from either some localized files in regular JDK or from some jar files in FFJ not part of FFJ code, like in lib/ext.
Davide, can we affect this in color editor?
Please have a look at the file http://www.netbeans.org/source/browse/core/src/org/netbeans/beaninfo/editors/ColorEditor.java?rev=1.29&content-type=text/x-cvsweb-markup Variables awtColorNames and systemColorNames were marked as NOI18N. I don't know why. If we are talking about these I think that this bug report is accurate and it should be fixed to NB3.3.
I'm not that sure. The things you're talking about are names of fields of some JDK classes (yes, those system* are modified a bit form the real field names). I, as a programmer, do much better like to see the real names of the fields. That is why the tabs are called AWT palette, Swing palette and System palette. It may be reasonable to use these three palettes only for code generation purposes (in form) and not for setting up the IDE (Wow, I'd like my editor to have SystemColor.activeCaptionBorder color background) But please do not try localize API. Just my 2 bits.
Again: I was talking about systemColorNames, awtColorNames. At least one of them can hardly be any class names while the other might be but there is another array with classes right above. So I suspect these are not used as class names but didn't check that thoroughly. If you would like to go on please have a closer look and fix this bug. Thanks.
Fixed in [main-trunk]. Next build available. Localizable are now items from AWT and Swing palette. The items from System palette reamin non-localizable since their names are programatic color names.
verified
Resolved for 3.4.x or earlier, no new info since then -> closing.