Red Hat Bugzilla – Bug 1233107
[ja_JP] Translation issues on services->my services page
Last modified: 2016-06-29 10:57:31 EDT
Created attachment 1040374 [details] All services Description of problem: Following translation issues have been observed on services->my services page. Please refer attached screenshot and TCMS link https://tcms.engineering.redhat.com/run/247967/#caserun_10014961 for more information. 1. 1.Click Services -> My Services from the navigation bar. All strings including an error message appear in English. (See the screenshot "All Services".) 2. 2.Click Services from left panel, click All Services, select any service, click on the top Configuration drop-down menu: All drop-down menus and items in tables appear in English. (See the screenshot "service page".) 3. Click Services from left panel, click All Services, select any service, click on the top Configuration drop-down menu: "Reconfigure" A page appearing after selecting "Reconfigure this service" has all English strings. (See the screenshot "Reconfigure this service".) 4. click on the top Policy drop-down menu: Edit Tags: A message "* Only a single value can be assigned from these Tag Categories" appears in English though the exact strings found in the translation file. 5. Reg #4: The message appearing in the instance is slightly different the one found in the file. A Message on the instance: * Only a single value can be assigned from these categories The corresponding strings found in the file: * Only a single value can be assigned from these Tag Categories 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:
Created attachment 1040375 [details] service page
Created attachment 1040376 [details] Reconfigure this service
Created attachment 1040377 [details] service tag message
Fixed in 5.6, moving to ON_QA for verification.
Verified on 5.6.0.10-rc2.1. Translations are available now. Moving bug to Verified as of now.
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