Bug 1356256

Summary: [RFE] SSUI should be able to set locales separately from Operations UI
Product: Red Hat CloudForms Management Engine Reporter: Chris Pelland <cpelland>
Component: InternationalizationAssignee: Shveta <sshveta>
Status: CLOSED ERRATA QA Contact: Shveta <sshveta>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: dajohnso, jhardy, jprause, mzazrivec, obarenbo
Target Milestone: GAKeywords: FutureFeature, i18n, RFE, ZStream
Target Release: 5.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ssui
Fixed In Version: 5.6.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1356254 Environment:
Last Closed: 2016-08-18 17:57:02 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:
Bug Depends On: 1356254    
Bug Blocks:    
Attachments:
Description Flags
Locales none

Description Chris Pelland 2016-07-13 20:22:19 UTC 
+++ This bug was initially created as a clone of Bug #1356254 +++

If you look into ManageIQ sources under config/locales, you will find Chinese and Japanese locale catalogs only. 

This is OK, since those are the only two languages for the OPS UI 100% translated. 

If we're talking about self-service, then you need to look into sources of the Self-Service UI, where you'll find much more catalogs merged (Spanish being one of them) -- all of these are 100% translated. 

Since SSUI is an angular application built on top of OPS rest-api, whenever SSUI asks the API -- what's the locale I need to use for this particular user? Then the OPS API can only respond with: English, Chinese or Japanese (you're not able to set anything else for the user).
Comment 2 Shveta 2016-08-02 22:32:59 UTC 
Created attachment 1186910 [details]
Locales

SSUI Is able to select languages separately from OPS UI.
Verified in 5.6.1.0.20160726144018_810a94f
Comment 4 errata-xmlrpc 2016-08-18 17:57:02 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/RHSA-2016-1634.html