Created attachment 894716 [details] Screenshot: Assignment editor Description of problem: Buttons which add a new data input/output assignment is not localized. See https://github.com/droolsjbpm/jbpm-designer/blob/6.0.x/jbpm-designer-client/src/main/resources/org/jbpm/designer/public/js/Plugins/propertywindow.js: text: "[ New Data Input Assignment ]" text: "[ New Data Output Assignment ]" header: 'Assignment Type' I think that there should be: text: ORYX.I18N.PropertyWindow.addInputAssignment text: ORYX.I18N.PropertyWindow.addOutputAssignment header: ORYX.I18N.PropertyWindow.assignType Please do not forget use default value and add this property to all supported localization files (en, ja, de, es, ru). Version-Release number of selected component (if applicable): 6.0.2 ER2 BPMS Expected results: These labels of buttons should be localized and it should depends on selected language. Additional info:
Despite new I/O Editor was introduced this issue is still actual. But with little changes. Properties without localization: text: "[ Input Assignment ]" text: "[ Input Mapping ]" text: "[ Output Mapping ]" https://github.com/droolsjbpm/jbpm-designer/blob/6.3.x/jbpm-designer-client/src/main/resources/org/jbpm/designer/public/js/Plugins/propertywindow.js But it seems like dead code because Mapping Editor is not in use any more. Am I right?
(In reply to Kirill Gaevskii from comment #1) > Despite new I/O Editor was introduced this issue is still actual. But with > little changes. > > Properties without localization: > text: "[ Input Assignment ]" > text: "[ Input Mapping ]" > text: "[ Output Mapping ]" > > https://github.com/droolsjbpm/jbpm-designer/blob/6.3.x/jbpm-designer-client/ > src/main/resources/org/jbpm/designer/public/js/Plugins/propertywindow.js > > > But it seems like dead code because Mapping Editor is not in use any more. > Am I right? The old Assignments Editor and DataInputs / DataOutputs editors aren't normaly used any more. There is a startup flag that can be used to trigger the use of these old dialogs instead of the new dataIOEditor. That's why the old code is still present.
Kirill, Even though this code can still be activated by using a startup flag, it doesn't make sense to do any more work on it. I'd suggest that we close the bug as "Won't Fix". If you agree, will you close it. Thanks.
I am agree.