Created attachment 1169799 [details] ja_JP Description of problem: For all the locales except, ko_KR and zh_CN, the UI alignment needs to be corrected. Please refer attached screenshots for reference. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 4.0.0.4-0.1.el7ev How reproducible: always Steps to Reproduce: 1. login to admin portal with any of the affected locales. 2. go to cluster->new->fencing policies. 3. Actual results: The UI alignment is not proper at some places. Expected results: The alignment should be proper. Additional info:
Created attachment 1169800 [details] de_DE
This issue is reproducible in 4.1.0.3-0.1.el7 as well. Changing the version accordingly.
I've checked english on the new patternfly dialogs in 4.2 and that works well. Moving to MODIFIED.
Not in any build, move to ON_QA when this is in some build.
(In reply to Oved Ourfali from comment #3) > I've checked english on the new patternfly dialogs in 4.2 and that works > well. > Moving to MODIFIED. Oved, Could you please check why was it missing from the latest upstream build?
Still not fixed in 4.2.0-0.4.master.el7
Can you show us a screenshot of what is not fixed in 4.2 master? it looks perfectly fine to me.
Created attachment 1348957 [details] ja_JP localization new It's the same as in first screenshot
See the problem now. I will see if I can address it.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Awesome, the text is aligned, now the help icon :) I'm using ovirt-engine-webadmin-portal-4.2.0-0.5.master.el7.noarch
Created attachment 1358284 [details] badly aligned help icon
Verified on ovirt-engine-webadmin-portal-4.2.0-0.6.el7.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.