Bug 1541917

Summary: [ja_JP] Text alignment correction needed on compute -> hosts -> new -> network provider window
Product: [oVirt] ovirt-engine Reporter: Bhushan Barve <bbarve>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.1CC: alkaplan, bbarve, bugs, lleistne, lsvaty, myakove, ylavi
Target Milestone: ovirt-4.2.4Keywords: i18n
Target Release: ---Flags: ylavi: ovirt-4.2+
ylavi: exception+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:44:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ja_JP_alignment none

Description Bhushan Barve 2018-02-05 08:13:50 UTC
Created attachment 1391389 [details]
ja_JP_alignment

Description of problem: For ja_JP locale, the text alignment needs to be corrected on compute -> hosts -> new -> network provider window. The last letter of the string 'Use cluster's default network provider' in Japanese fall on the new line. Please refer attached screenshot.


Version-Release number of selected component (if applicable):
4.2.1.3-0.1.el7

How reproducible:
always

Steps to Reproduce:
1. Login to Admin portal with ja_JP locale
2. Go to compute -> hosts -> new -> network provider window.
3. Observe the Japanese equivalent string for 'Use cluster's default network provider'.


Actual results:
The last letter is on the new line

Expected results:
The whole string should be on a single line.

Additional info:

Comment 1 Lucie Leistnerova 2018-06-11 07:38:22 UTC
Checkbox label not truncated

verified in ovirt-engine-webadmin-portal-4.2.4.2-0.1.el7_3.noarch

Comment 2 Sandro Bonazzola 2018-06-26 08:44:37 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.