Hide Forgot
Created attachment 818236 [details] Japanese error message Description of problem: The current translation of error message "Something went wrong" seems to be appropriate as software error message. Version-Release number of selected component (if applicable): 4.0 How reproducible: 100% Steps to Reproduce: Unable to provide specific steps to produce this error message. In my case, creating second instance resulted in this error. Please refer to screenshots (en-US and ja-JP) The string in question is the first sentence. Actual results: どこかがおかしくなりました ! Expected results: It should be better to change it to either "問題が発生しました" or "何らかの問題が発生しました" Additional info: File: for_use_horizon_openstack-dashboard-translations_ja.po #: templates/500.html:67 msgid "Something went wrong!" msgstr "どこかがおかしくなりました !"
Created attachment 818240 [details] The corresnponding en-US error message
Correction: "The current translation of error message "Something went wrong" seems to be appropriate as software error message." in the description above meant to be: The current translation of error message "Something went wrong" does not seem to be appropriate as software error message. This will be discussed with the upstream ja-JP user group. I will report the progress here.
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 852996 [details] ja-JP Error message translation improved
Thank you Ami for help reproducing this error message. Verified on the latest RHOS 4.0.z puddle. Screenshot attached. 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. https://rhn.redhat.com/errata/RHBA-2014-0046.html