Bug 1340341

Summary: [ja_JP] The text alignment on Optimize -> Bottlenecks -> Reports page, needs to be corrected.
Product: Red Hat CloudForms Management Engine Reporter: Bhushan Barve <bbarve>
Component: UI - OPSAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED ERRATA QA Contact: Bhushan Barve <bbarve>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: bbarve, dajohnso, hkataria, jhardy, mpovolny, myamamot, obarenbo
Target Milestone: GAKeywords: i18n
Target Release: 5.7.0   
Hardware: All   
OS: Linux   
Whiteboard: i18n
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 12:55:07 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
ja_JP_alignment none

Description Bhushan Barve 2016-05-27 06:04:31 UTC
Created attachment 1162369 [details]
ja_JP_alignment

Description of problem: The text alignment on Optimize -> Bottlenecks -> Reports page, needs to be corrected.

The last letter of the string 'Event Group' in Japanese, is on the next line. It should be on the same line ideally.


Version-Release number of selected component (if applicable):
   5.6.0.7-beta2.6

How reproducible:
 always

Steps to Reproduce:
1. login with ja_JP locale.
2. Go to Optimize -> Bottlenecks -> Reports page
3. Observe the string 'Event Group'

Actual results:
The last letter is on the second line.

Expected results:
The whole string should be in one line.

Additional info:

Comment 2 Mie Yamamoto 2016-09-22 00:35:15 UTC
The string is fit in one line

Comment 4 errata-xmlrpc 2017-01-04 12:55:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0012.html