Bug 1233586

Summary: [ja_JP] Translation issues on Clouds - Instances - Instances by Provider page
Product: Red Hat CloudForms Management Engine Reporter: Bhushan Barve <bbarve>
Component: InternationalizationAssignee: Dan Clarizio <dclarizi>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4.0CC: bbarve, jhardy, lijli, obarenbo
Target Milestone: GAKeywords: Translation
Target Release: 5.5.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-03 09:22:38 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
provider2
none
provider1 none

Description Bhushan Barve 2015-06-19 08:47:23 UTC 
Created attachment 1040789 [details]
provider2

Description of problem: Following translation issues have been observed on Clouds - Instances - Instances by Provider page. Please refer attached screenshot and TCMS link https://tcms.engineering.redhat.com/run/247967/#caserun_10037131 for more information.

1. The title 'Instances by Provider' is untranslated.

2. The drop-downs for configuration, policy, lifecycle are untranslated as well as their tool-tips. Also the tool-tips for grid/tile/list view are not translated.

3. The page which opens after clicking on 'provision instances' under lifecycles drop-down has a table in which table headers are not translated.

Please refer attached screenshots provider1 and provider2 


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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Bhushan Barve 2015-06-19 08:56:01 UTC 
Created attachment 1040793 [details]
provider1
Comment 3 Lijun Li 2015-12-03 09:22:38 UTC 

*** This bug has been marked as a duplicate of bug 1225427 ***