Bug 869755 - Japanese : Translation required in Japanese for Setting button and error message in Settings Page
Summary: Japanese : Translation required in Japanese for Setting button and error mess...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Shveta
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-24 18:22 UTC by Shveta
Modified: 2012-12-12 15:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-12 15:18:56 UTC
Embargoed:

Attachments (Terms of Use)
Settings Button and error message (65.24 KB, image/png)
2012-10-24 18:22 UTC, Shveta 		no flags Details
header fixed (46.68 KB, image/png)
2012-10-24 18:46 UTC, Shveta 		no flags Details
View All

Description Shveta 2012-10-24 18:22:46 UTC 
Created attachment 632916 [details]
Settings Button and error message

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Translation required in japanese for all the following
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Shveta 2012-10-24 18:46:54 UTC 
Created attachment 632925 [details]
header fixed

Tested in puddle 6 ....fixed


rpm -qa|grep aeolus
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-0.13.21-1.el6cf.noarch
rubygem-aeolus-cli-0.7.6-1.el6cf.noarch
aeolus-conductor-doc-0.13.21-1.el6cf.noarch
aeolus-all-0.13.21-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.21-1.el6cf.noarch
Comment 3 James Laska 2012-12-12 15:18:56 UTC 
CloudForms-1.1 shipped with aeolus-conductor-0.13.24-1.el6cf, aeolus-configure- 2.8.11-1.el6cf, imagefactory-1.0.2-1.el6cf, iwhd-1.5-2.el6, and oz-0.8.0-6.el6cf

Marking this bug CLOSED CURRENTRELEASE.  Please reopen if the problem has not   been addressed in the 1.1 product.
Note You need to log in before you can comment on or make changes to this bug.