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.
build 0830, ja_JP 1. Create BPEL Module 2. Create BPEL process 3. Drag and Drop on the diagram any of items from the palette Its name will be shown on the diagram not from pseudo localized bundle file. User could change the name of the object, but on the other hand, its being named with a word that describes the kind of object it is, based on palette, so that means it should come from pseudo localized bundle file also.
Created attachment 48025 [details] image
Fixed.
Vladimir, the fix you've made is not appropriate since it provides localization for bpel element names (xml tags), not for their representation in the UI. Reopening the issue.
QE: should default names (Assign1, Reply1, etc) be localized or not?
this is a good question and comes up often in other areas that have pallette and properities display. if the name is not going to be or need to be a reserved word in the code or spec, then these words could be localizable. We know user might change them anyway, but it seems that the original names were chosen with some english context - Assign1 is chosen since the pallette item/function is assign, and so on thus the word Assign gives a clue to the user about what this item is. If so, then seems its ok to give same clue to user of translated. if there is some spec however that restricts it to be only en, or if the users might be used to seeing the words only in english, then it might not be done. I realize there is a diff between the name of the item on the pallette and the name of this particular item as to some spec -- that is, the spec might say that this is an Assign kind of item, and that is on the pallete and users are used to it so those perhaps might not be allowed to be translated. but the actual name of this instance of the item Assign1, is just a name, and might be ok to translate. summary - it depend on the technology/api and user patterns. ken.frank@sun.com
This name is used as a tag name and can't be translated. I rollback changes. Closing as won't fix.
just to clarify, tag names cannot be non ascii ? so that if user would go the code/file where the tag names are (or props editor if there is one for this) and change the name of the item, that project or code would not compile or run ? ken.frank@sun.com
This name is used not only as a tag name but as internal value which can't be translated.
if user changes tag name to use non ascii, in design or properties or other window, ie change Receive1 to some asian characters, does it mean that the code or app will not compile or run ok ? if so, then I think some checking for this could happen and not allow the change. ken.frank@sun.com
please answer the previous question since it seems that if user changed tag name on their own it could break the functionality ? (even if not translated, user can change value of any item in code or properties) if so, seems like an issue and that some warning could be given in ui. please let me know if it should be filed. ken.frank@sun.com
User can't change the name of tag because the names are defined in BPEL specification. So, default name is taken from tag name, I don't see any issue or problem if default name is not translated. User can change the name later.
thanks for clarifying about this. ken.frank@sun.com
verified using Build 200810130101 and the tag names are the same as shown on the palete.