Created attachment 1358565 [details] Table headers truncation Description of problem: For ja_JP locale, the menus on compute->virtual machines-> disks -> new -> direct LUN page are truncated. The issue is observed for menu items on LUN->Targets tab at the bottom. Please refer attached screenshot. This issue is observed for all locales except zh_CN and ko_KR. Please refer attached screenshot. Version-Release number of selected component (if applicable): 4.2.0-0.5.master.el7 How reproducible: always Steps to Reproduce: 1. Login to admin portal with any of the above mentioned locales. 2. Go to compute->virtual machines-> disks -> new -> direct LUN page 3. At the bottom, click on LUN->Targets and observe the table headers. Actual results: Table headers are getting truncated. Expected results: Table headers should be visible properly. Additional info:
My patch did not work out, and Shani is already working on this. Reassigning and un-targeting.
The fix is included in the ovirt-engine-4.2.0.1 tag. Moving to ON_QA.
Checked with Version:4.2.0.2-0.1.el7 The mentioned issue still exists for table headers on compute->virtual machines-> disks -> new -> direct LUN page. Please refer attached screen-shots for reference. Moving it back to assigned.
Created attachment 1369886 [details] ja_JP_truncation_4.2.0.2-0.1.el7
Created attachment 1369887 [details] fr_FR_truncation_4.2.0.2-0.1.el7
Shani, all these patches are included in 4.2.1. Do we need anything from the localization team, or are your patches all we need? If so, please retarget to 4.2.1 and move to ON_QA.
The ellipsis (...) at the end of a too long table's header and the added tooltips supposed to solve the issue, so it does not depend on the localization team.
Checked with 4.2.1.3-0.1.el7 Looks fine now for all the mentioned locales. Marking it as verified.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.