Bug 822684 - CloudEngine String Updates
Summary: CloudEngine String Updates
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-17 18:55 UTC by Matt Reid
Modified: 2020-03-27 18:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Matt Reid 2012-05-17 18:55:39 UTC
Description of problem:
After going through the String file for CloudEngine, there are a few typos I wanted to point out in case they haven't already been fixed.

General string updates:
"succesfully" is used once, and while most of the time UUID is capitalized, it's lowercase at least once. It'd be nicer if UUID was consistently used in all caps.


The following could use some additional words/wording tweaks:
Application Blueprint XML file doesn't resolve [to a?] valid XML file

Choose one of the following options to upload [an] application blueprint XML file

The Application Blueprint '%{deployable}' contains a Component Outline (UUID %{uuid}) in the wrong Cloud[,] ('%{wrong_env}' should be '%{environment}') and cannot be used.

seems to be not valid application blueprint XML: %{msg} -> That is not a valid  application blueprint XML file: {msg}. (Not exactly sure what this one is referring to, but as-is, its a bit awkward, my suggestion may not be correct.)

Cannot launch a[n] Application in this Cloud Resource Zone. It has been disabled.

The markup and component outline references in "%{name}" were succesfully validated. You may now save the component outline, and create a[n] application blueprint.

There are no provider accounts associated with [the] cloud of selected cloud resource zone. (Not sure how best to fix this, but I think it could use a little attention)

----

These are coming from the EN.po file, which I think was up to date as of this week.

Not sure the best component to file this against, please modify that if this isn't the best.

Comment 4 Giulio Fidente 2012-10-09 14:01:14 UTC
Moving this back to 'MODIFIED' as not all the things reported seem to have been fixed.


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