[jira] [Closed] (CLOUDSTACK-4502) G11N: English fall back mechanism is not supported on CCP builds

["Sreekanth Challa (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sreekanth Challa closed CLOUDSTACK-4502.
----------------------------------------

    Resolution: Invalid
    
> G11N: English fall back mechanism is not supported on CCP builds
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4502
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4502
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>         Environment: Cent OS 6.3: Mgmt Server
> Client OS: Windows 7, Windows 2008
>            Reporter: Sreekanth Challa
>              Labels: EN,, fallback
>             Fix For: 4.2.0
>
>         Attachments: French_LoginPage_MainUI.jpg, KOR_Login_UI_EULA.jpg, Spanish_Main UI.jpg
>
>
> EN Fall back mechanism is not supported on CCP builds, when web console is accessed on Korean, Spanish, French & German client OS.
> Steps to reproduce:
> 1. Install the latest build CloudPlatform-4.2-514-rhel6.3.tar.gz
> 2. Open the web console(Mgmt Server UI) on Korean, Spanish, French & German client OS.
> 3. Check the login page
> 4. Click on the 'Login' button and check the EULA & main UI
> Expected Result: Since the L10N support for other languages(Catalan,Korean, German, French, Italian, Spanish, Arabic, Norwegian, Brazilian Portuguese) are removed on CCP builds, the UI should fall back to English when it is accessed through these unsupported localized environments.
> Actual Result: The login page, EULA and the main UI should fall back to English when the UI is accessed through unsupported localized environments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira