Hide Forgot
Description of problem: "Red Hat Search" and "Red Hat Documentation" subtabs are unlocalized. Version-Release number of selected component (if applicable): 3.3.0-0.22 How reproducible: 100% Steps to Reproduce: 1. Open Web Admin Portal in a given locale 2. Click on "Data Centers" tab and select one item in the list. 3. Check the subtabs in the details pane. Actual results: "Red Hat Search" and "Red Hat Documentation" subtabs are unlocalized. Expected results: Both should be localized. Additional info: I have attached a screenshot.
Created attachment 799698 [details] Unlocalized subtabs under Data Center tab
Created attachment 799710 [details] Red Hat Search subtab unlocalized
In addition to the unlocalized subtab labels, I have also attached a screenshot of unlocalized strings on the "Red Hat Search" subtab.
Just found that the same subtabs appear under other resource tabs as well: Clusters Host Storage Virtual Machines Templates
"Red Hat Search" and "Red Hat Documentation" tabs are dynamically added to the application via the ui plugins infrastructure. each plug-in must supply a set of names in all of RHEV's supported locales, but first we must support localization in the ui-plugins infrastructure.
This bug has also found into fr-FR Portal
there is a chance that the ui-plugins infrastructure would have to supply the currently-selected locale for the ui-plugins to consume (so bugs such as bug 1009722 can be solved).
einav - scope of effort to support this for the changes to the main gui (buttons/context menu added)? on how uiplugins would support it for their dialogs?
(In reply to Itamar Heim from comment #8) > einav - scope of effort to support this for the changes to the main gui > (buttons/context menu added)? main-tab/sub-tab/dialog-title/button/context-menu can probably all be covered by the same effort. the ui-plugins-infrastructure will need to be able to consume dynamic resources [i.e. resources (e.g. .properties files) supplied by the ui-plugin]. not trivial IMO. > on how uiplugins would support it for their dialogs? each custom dialog/main-tab/sub-tab will need to take care of its own localization (as they typically display external content). we can only supply the current GUI locale to be consumed by the external content. this is the "supply current GUI locale" part of the RFE subject. this shouldn't take long - sounds like another method/property of 'getCurrentEngineLocale' or similar.
I don't see us prioritizing this work. For specific plugins that are built in, like the dashboard, we solve this as part of the plugin itself. Closing this as wontfix.