Bug 1026594 - [ja_JP] Translation of Suspended Instance is grammatically incorrect
Summary: [ja_JP] Translation of Suspended Instance is grammatically incorrect
Keywords:
Status: CLOSED DUPLICATE of bug 1026284
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.0
Assignee: RHOS Maint
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 03:08 UTC by Mie Yamamoto
Modified: 2013-11-11 07:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 07:27:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
Translation of Suspend Instance - grammatically incorrect (162.87 KB, image/png)
2013-11-05 03:08 UTC, Mie Yamamoto
no flags Details

Description Mie Yamamoto 2013-11-05 03:08:46 UTC
Created attachment 819467 [details]
Translation of Suspend Instance - grammatically incorrect

Description of problem:
Translation of suspended Instance is grammatically incorrect

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" menu and change the language to Japanese.
3.Click on Admin-System Panel-Instances tab from the left side panel, click & check the drop-down list "Suspend Instance"

Actual results:
インスタンスの休止しました。

Expected results:
インスタンスを休止しました。

Additional info:
similar bugs
1026160
1026284
1026592

Comment 2 Yuko Katabami 2013-11-10 21:06:19 UTC
Reported to the upstream ja-JP user group on 8 Nov and is currently under discussion.

Comment 3 Yuko Katabami 2013-11-11 07:27:52 UTC
This bug is caused by the following string and is the same issue as BZ#1026284

#: tables/actions.py:560
#, python-format
msgid "%(action)s %(data_type)s"
msgstr "%(data_type)sの%(action)s"

*** This bug has been marked as a duplicate of bug 1026284 ***


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