Bug 1286521

Summary: [ja_JP][zh_CN] Some strings on configuration->my settings->default view sub-tab are not translated.
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.5.0CC: bbarve, hkataria, jhardy, kkrothap, lijli, mpovolny, obarenbo
Target Milestone: GAKeywords: Translation
Target Release: 5.6.0   
Hardware: All   
OS: Linux   
Whiteboard: i18n
Fixed In Version: 5.6.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:13: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
container untranslated strings none

Description Bhushan Barve 2015-11-30 07:02:51 UTC 
Description of problem: Some strings on configuration->my settings->default view sub-tab are not translated.


Version-Release number of selected component (if applicable):


5.5.0.12-rc2.20151124135609_653c0d4


How reproducible:
always

Steps to Reproduce:
1. Launch the application in ja_JP locale
2. Go to configuration->my settings->default view
3. Observe the strings under 'container' (コンテナー )

Actual results:
Many of the strings are untranslated.

Expected results:
All the strings should be translated.

Additional info:
Please refer attached screenshot.
Comment 2 Bhushan Barve 2015-11-30 07:03:20 UTC 
Created attachment 1100364 [details]
container untranslated strings
Comment 3 Milan Zázrivec 2016-06-02 11:43:33 UTC 
Fixed in 5.6, moving to ON_QA for verification.
Comment 4 Krishna Babu K 2016-06-17 13:16:53 UTC 
Verified on cfme 5.6.0.10-rc2.1. Translations are available now.
Moving bug to Verified as of now.
Comment 6 errata-xmlrpc 2016-06-29 15:13: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://access.redhat.com/errata/RHBA-2016:1348