Red Hat Bugzilla – Bug 1026555
[ja_JP] Migrate Instance (in Admin > Instance) does not fit in the pull down menu
Last modified: 2015-02-15 17:02:38 EST
Created attachment 819419 [details]
migrate instance in the pull down menu
Description of problem:
Migrate instance does not fit in the pulldown menu
Version-Release number of selected component (if applicable):4.0
How reproducible: 100%
Steps to Reproduce:
1.Click on Admin-System Panel-Instances tab from the left side panel
2.Click on the More pull down
Migrate Instance (インスタンスのマイグレーション）
インスタンスの移行？ can be used to make it a little shorter.
Reported to the upstream ja-JP user group on 8 Nov and is currently under discussion.
The button names are auto-generated. If we're happy that the new translation for 'migration' is appropriate in the other places (success/error messages, etc.) this should be doable, otherwise we may have to leave it as in for the time being.
Translation is unlikely to be changed after discussion with the upstream ja-JP user group because the current translation is more appropriate for other usages (e.g. live migration) and it is better to make it consistent across the entire UI strings.
The string "Migrate Instance" in the dropdown menu is wider than the space provided, however it is not truncated (all characters are still visible).
Also this issue is present in Firefox, but not in Google Chrome.
For those reasons, the priority may not be high, but it would be great if the width can be extended to fit the entire string at some stage.
Thank you for the update, Yuko.
Created attachment 878930 [details]
Migrate Instance -- box width fixed
During the upstream Icehouse translation review, I found that this issue has been fixed.
I am not sure what status change I should make now, as it is still not pushed into RHEL OSP.
Julie, should I wait until this can be verified in Red Hat version?
Thanks for the update Yuko, it's good news. I think there are 2 things we can do:
* Close the bug with "NEXTRELEASE" in the details dropdown menu (and leave a comment indicating this is fixed in RHEL OSP 5.0), or
* Wait for the RHEL OSP 5 packages to be available and verify on a OSP 5 system.
In general option #2 is preferred but because this is a small, low priority/severity bug I think either is fine here. Let me know. Thank you!
Thank you for your prompt reply.
I choose option #2.
Ok! Let's leave the bug open until then. I took the liberty of assigning you to verify it.
Nps. Thank you Julie.
This was fixed during upstream Icehouse and should already be available in our packages.
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.