Bug 1284818

Summary: [ALL LANG] Unlocalized strings in Edit HTML Component dialog.
Product: [Retired] JBoss BPMS Platform 6 Reporter: Lijun Li <lijli>
Component: Business CentralAssignee: Eder Ignatowicz <eignatow>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: kverlaen, qe-i18n-bugs
Target Milestone: DR2Keywords: Translation
Target Release: 6.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:03:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Unlocalized strings in Edit HTML Component dialog none

Description Lijun Li 2015-11-24 09:47:12 UTC 
Description of problem:
Unlocalized strings in Edit HTML Component dialog.

Version-Release number of selected component (if applicable):
6.2.0.ER 5

How reproducible:
100%

Steps to Reproduce:
1. Login bpms with no en_US locale.
2. Click Extensions -> Plugin Management from top menu bar.
3. Click New -> New Perspective drop-down menu.
4. Enter the name and OK.
5. Click Components in Perspective Editor page.
6. Drag HTML Component to the center column and check on the Edit HTML Component dialog.

Actual results:
Unlocalized strings in Edit HTML Component dialog.

Expected results:
It should be localized.

Additional info:
Please see the attached screen-shot.
Comment 1 Lijun Li 2015-11-24 09:48:06 UTC 
Created attachment 1098100 [details]
Unlocalized strings in Edit HTML Component dialog
Comment 3 Eder Ignatowicz 2016-02-11 18:28:17 UTC 
Fixed:
master: https://github.com/uberfire/uberfire-extensions/commit/5f9e274b7c6f016e75eaf480d7d18c8efa3f56af

0.8.x https://github.com/uberfire/uberfire-extensions/commit/cd8eb49f9fde36ae380b4a83e57a93c58379c82e
Comment 4 jsoltes 2016-03-02 15:02:53 UTC 
The issue is still there in bpm-suite 6.3.0.DR2.