Bug 1429458 - UI: Some texts are not translated in Navigation
Summary: UI: Some texts are not translated in Navigation
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Milan Zázrivec
QA Contact: Satyajit Bulage
URL:
Whiteboard: i18n
Depends On:
Blocks: 1444884
TreeView+ depends on / blocked
 
Reported: 2017-03-06 12:21 UTC by Satyajit Bulage
Modified: 2019-12-23 09:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1444884 (view as bug list)
Environment:
Last Closed: 2019-07-31 20:14:05 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot showing untranslated navigation. (94.18 KB, image/png)
2017-03-06 12:21 UTC, Satyajit Bulage
no flags Details

Description Satyajit Bulage 2017-03-06 12:21:10 UTC
Created attachment 1260376 [details]
Screenshot showing untranslated navigation.

Description of problem: In navigation, Certain texts like main navigation and sub-navigation is not translated. (For more details see attached screenshot).

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


How reproducible:100%


Steps to Reproduce:
1.Change Language to Japenese.
2.See Navigation
3.

Actual results: Navigation is not translated 


Expected results: Navigations should be translated.


Additional info:

Comment 2 Milan Zázrivec 2017-04-06 15:02:25 UTC
This problem is simply a matter of having up-to-date translations.

Comment 6 Milan Zázrivec 2018-09-05 11:09:14 UTC
These two strings: "Ansible" and "Ansible Tower" are not meant to be translated in simplified Chinese.

Comment 7 Satyajit Bulage 2018-09-05 15:45:14 UTC
Able to see "Automation" navigation is translated not the Ansible and Ansible Tower as per Comment 6

Verified Version: 5.8.5.0.20180821175127_9cfc0ea


Note You need to log in before you can comment on or make changes to this bug.