Red Hat Bugzilla – Bug 1025640
[ja_JP] Translation of description text in "Allocate Floating IP" window can be improved for better readability
Last modified: 2016-04-26 19:13:23 EDT
Description of problem:
Japanese translation of description in "Allocate Floating IP" window can be improved for better readability.
Version-Release number of selected component (if applicable): 4.0
How reproducible: 100%
Steps to Reproduce:
1. Log in to Dashboard with admin account.
2. Click "Settings" and change the language to Japanese
3. Select "Project" tab on the left panel and click "Access & Security" under "Manage Compute"
4. Select "Floading IP" tab on the main panel and click "Allocate IP To Porject"
5. In "Allocate Floating IP" window, check text shown under "Description" ("Allocate a floating IP from a given floating IP pool.")
Floating IP を指定した Floating IP プールから割り当てます。
(because of the order of clauses, this can be interpreted in two different ways, and incorrect interpretation is: "Allocate from Floating IP pool which you have given Floating IP)
Change the order of clauses to:
指定した Floating IP プールから Floating IP を割り当てます。
msgid "Allocate a floating IP from a given floating IP pool."
msgstr "Floating IP を指定した Floating IP プールから割り当てます。"
This will be discussed with the upstream ja-JP user group.
I will report the progress here.
Reported to the upstream ja-JP user group on 8 Nov and is currently under discussion.
This translation fix has been merged into the upstream Havana Stable Update.
Moving the status to POST.
Created attachment 850737 [details]
Japanese translation for Allocate Floating IP is fixed
Verified on the latest RHOS 4.0.z puddle.
(Note: Japanese translation for the verb "allocate" remains the same as we came to agreement in the upstream user group, however the sentence order / structure has been improved according to my suggestion)
Moving the status to VERIFIED.
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.