Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mw server translations #16483

Closed
wants to merge 2 commits into from

Conversation

tumido
Copy link
Member

@tumido tumido commented Nov 16, 2017

Add Translation for Middleware servers so they appear correct in Alert profile listings.

Fixes: BUG 1511653
Depends on (for smaller change set): #16482

Before:
image

After:
image

cc @abonas

@miq-bot
Copy link
Member

miq-bot commented Nov 16, 2017

Checked commits tumido/manageiq@2f3edad~...75fb0b9 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0
3 files checked, 1 offense detected

**

  • 💣 💥 🔥 🚒 - Linter/Yaml - missing config files

@tumido
Copy link
Member Author

tumido commented Nov 16, 2017

@miq-bot add_label internationalization, middleware, bug

@miq-bot
Copy link
Member

miq-bot commented Nov 16, 2017

@tumido Cannot apply the following label because they are not recognized: middleware

@tumido
Copy link
Member Author

tumido commented Nov 16, 2017

@miq-bot add_label providers/middleware

@abonas
Copy link
Member

abonas commented Nov 16, 2017

@tumido iiic, this PR contains another commit from a different PR?
@JStickler please review

@abonas
Copy link
Member

abonas commented Nov 16, 2017

@mzazrivec please review

@tumido
Copy link
Member Author

tumido commented Nov 16, 2017

@abonas yes. I can't build this PR upon master if the master is not in sync with itself. So once the dependent PR is merged (which is here as the first commit) the change set would include only the MW related part.

Copy link

@JStickler JStickler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure you use the proper spelling and capitalization for Red Hat and VMWare to comply with their corporate branding.
I’m working under the assumption that most of the strings in these files are UI labels for fields and actions and should be consistently capitalized as Title Case (that is, all words capitalized).
It may be that some of the strings that I marked weren’t field or action labels but messages displayed to the user. User messages should be Sentence Case capitalization (capitalize first word only) and you can ignore my attempts to change them to Title Case capitalization.
Also noted instances where I wasn’t sure if I was looking at a parameter or a field label (should this be one word or three?).

# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Openstack::InfraManager::Host (plural form)
_("Hosts (OpenStack)")
# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Redhat::InfraManager::Host
_("Host (Redhat)")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Red Hat is two words, both should be capitalized.

# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Redhat::InfraManager::Host (plural form)
_("Hosts (Redhat)")
# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Vmware::InfraManager::Host
_("Host (Vmware)")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VMware should have the first two letters capitalized.

# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Hawkular::MiddlewareManager::MiddlewareServerEap (plural form)
_("Middleware Servers (EAP)")
# TRANSLATORS: en.yml key: dictionary.model.ManageIQ::Providers::Hawkular::MiddlewareManager::MiddlewareServerWildfly
_("Middleware Server (Wildfly)")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WildFly should have the "F" capitalized.

# TRANSLATORS: file: db/fixtures/miq_product_features.yml
_("Everything under Cloud Object Stores")
_("Everything under Cloud Object Store Containers")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should "store" be "storage"? (I'm not sure of the correct terminology here)

@@ -3282,6 +3315,10 @@
# TRANSLATORS: file: db/fixtures/miq_product_features.yml
_("Re-check Authentication Status of Physical Infrastructure Providers")
# TRANSLATORS: file: db/fixtures/miq_product_features.yml
_("Management Console")
# TRANSLATORS: file: db/fixtures/miq_product_features.yml
_("Open a management console")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open a Management Console
(to be consistent with the title capitalization used elsewhere)

@@ -33368,7 +32319,7 @@ msgstr ""
msgid "new_flavor_id cannot be nil"
msgstr ""

msgid "no %{table} credentials defined"
msgid "no Provider credentials defined"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No Provider credentials defined

@@ -33389,18 +32340,15 @@ msgstr ""
msgid "no parent_manager to ems"
msgstr ""

msgid "no yml file found for name \"%{name}\""
msgid "no uid_ems_array defined for linking to service"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No uid_ems_array defined for linking to service

msgstr ""

msgid "not connected to ems"
msgid "no yml file found for name \"%{name}\""

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No yml file found for name "%{name}"

msgid "time_profile must be passed if interval name is 'daily'"
msgstr ""

msgid "unable to execute script, file name [%{file_name} does not exist]"
msgid "unable to execute script, file name [%{file_name}] does not exist"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unable to execute script....

@@ -7488,7 +7534,22 @@ msgstr ""
msgid "Data Points"
msgstr ""

msgid "Data Store does not exist, unable to add disk"
msgid "DataSource - Connection Creation Time"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datasource - Connection Creation Time

(Datasource has been lower case, not camel case, through the rest of these files. Change the next couple of strings to be consistent.)

Copy link

@JStickler JStickler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure you use the proper spelling and capitalization for Red Hat and VMWare to comply with their corporate branding.
I’m working under the assumption that most of the strings in these files are UI labels for fields and actions and should be consistently capitalized as Title Case (that is, all words capitalized).
It may be that some of the strings that I marked weren’t field or action labels but messages displayed to the user. User messages should be Sentence Case capitalization (capitalize first word only) and you can ignore my attempts to change them to Title Case capitalization.
Also noted instances where I wasn’t sure if I was looking at a parameter or a field label (should this be one word or three?).

@mzazrivec
Copy link
Contributor

That commit updating gettext catalogs should not be included. If you need to add pretty model
names, just edit locale/en.yml and that's it.

Updating gettext catalogs is needed only when you want to upload the strings into Zanata
for translations. And I'm pretty sure that's not what you're doing here.

@chessbyte chessbyte requested a review from mzazrivec November 17, 2017 14:20
@chessbyte chessbyte self-assigned this Nov 17, 2017
@tumido
Copy link
Member Author

tumido commented Nov 17, 2017

@mzazrivec, @JStickler, I'm gonna close this PR, since @mzazrivec explained it's not needed to do it this way. I got wrong impression from the MIQ i18n docs that I need translations for new strings introduced. So I've tried to put things into order. The wrong way. Let's try it once more and better. Sorry for the clutter. IMO this PR's review by @JStickler should not be wasted and used in strings corrections later.

@mzazrivec
Copy link
Contributor

@tumido All you need to do is change locale/en.yml just as you did in this PR. That's all you need
to do really.

@abonas
Copy link
Member

abonas commented Nov 19, 2017

@tumido why did you close the PR? it seems that you can reopen it, fix the file that @mzazrivec pointed to, take into account @JStickler review and it's good to go

@mzazrivec
Copy link
Contributor

@abonas There's #16492 for this.

@tumido tumido deleted the add_mw_server_translations branch June 26, 2018 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants