moving to mobility component

I do not know whether it is good or not to have localized names in the palette.
Especially for the name "Exit Command" which "Exit" word could be localized and
"Command" word must not be localized. Therefore it can result into a state where
half of palette is localized and half is not. It includes all commands and elements.

Its a good point; are there some words in pallette that are reserved
and should not be translated, since might refer to some api or spec ?

If so, then there can be some ways to proceed -

- don't make these translatable since users might get confused if they are used
to seeing these in english due to being from a spec/api

- have them translatable but make sure not to place the translated words in the code

- don't translate but have the tooltips show the translated names

Can you give more information about which  words in pallette or drawing
area are not to be translated and reason for it ?

ken.frank@sun.com

Following words are representing a MIDP/custom class therefore they must not be
translated:
Displayable, Alert, Canvas, Form, List, TextBox, SplashScreen, WaitScreen
Command,
Item, ChoiceGroup, DateField, Gauge, ImageItem, Spacer, StringItem, TextField,
TableItem,
Font, Image, Ticker, SimpleCancelable, SimpleTableModel,
SVG*

Also word "Back" in "Back Command" is defined by a MIDP specification therefore
very likely it should not be translated too.

I am attaching a screen of palette. Red color highlights non-translatable word,
yellow highlights maybe-translatable word and green highlights translatable word.

When I am looking at the screenshot, i think the palette will not look nice with
translated words.

Created attachment 32934 [details]
Palette with highlighted words

Would it be confusing to users if there was a translatable display name
for the items on pallette, ie ImageItem. be shown as "Image Item"
even though in code it will need to stay as ImageItem ?

or are there tooltips for each palette item that do have localizable words that
would include the words for translations of Image Item ?

ken.frank@sun.com

Then I would like proposed following solution: For example:
Display name = ImageItem
Tooltip = Image Item for Form

Current implementation behaves similarly to FormEditor (component short name as
display name, component fqn as tooltip). The fix would affect many parts of the
Designer code including custom components modules (like TableItem, SVG module,
...) which may be risky. Because of that setting "Target Milestone" to "Dev". In
NetBeans 6.0 it has to be fixed.

Check out the latest labels in Swing palette. They are derived from Swing component names ("Tabbed 
Pane" for "JTabbedPane"). So I think they should be localized, but I'm not sure whether they really are.

for latest items for swing palette, if they are in the bundle file,
and there is not #NOI18N comment, and they written as separate words,
ie "Tabbed Pane", they will be localized.

Is this done for nb55 or 551 or for 6.0 ?
if for 551 or 6, it wont be localized yet since those releases are in progress.

Please let me know which jars/bundle files have these labels and I will make sure
to test now about them to make sure the localizable values really do appear.

ken.frank@sun.com

As for Swing palette, for 6.0 all the standard component names are placed in a 
bundle, so they can be localized. The file is: 
form/src/org/netbeans/modules/form/resources/Bundle.properties.

However, I'm not sure if translating the standard Swing component names is a 
good idea. The component names match the class names closely, translated names 
might be confusing and make the orientation more difficult.

I think its  decision of the developers and xdesign
to decide if these should be translated or not.

Please let me know decision when it happens so
we can i18n test properly, and not translate those items
if they should not be translated.

ken.frank@sun.com

Personally I would like to have it e.g.:
If a component is "JTextField", then the display name would be "Text Field" and
particular key/value pair in the Bundle.properties would be marked with "#NOI18N".

I have the opposite opinion. Sorry for a bit of Czech language here...

I think if the user prefers localized enviroment which means working with menu items like "Novy 
Soubor", "Novy Projekt", "Smaz", etc., then she/he would prefer to work with palette items called 
"Tabulka" instead of "Table", "Textove Pole" instead of "Text Field", and "Tlacitko" instead of "Button".

It really is user's choice whether to use localized IDE or English IDE. If the user picks localized IDE, the 
IDE should all terms that can be localized in selected language. So only term that cannot be localized 
should be show in original version (e.g. JTable cannot be localized, but Table can be).

I suggest to localize palette items.

Designer 1 has been removed. Therefore reassigning to Designer 2 module.

Fixed in main trunk.

verified

verified build 20070920