Bug 1007173 - [ja-JP][SAM Web GUI] Unlocalized string: "Name"
[ja-JP][SAM Web GUI] Unlocalized string: "Name"
Product: Subscription Asset Manager
Classification: Red Hat
Component: katello (Show other bugs)
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Katello Bug Bin
Depends On:
Blocks: sam20-tracker
  Show dependency treegraph
Reported: 2013-09-12 00:45 EDT by Aiko
Modified: 2013-12-02 15:45 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-02 15:45:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Unlocalized "Name" (English and Japanese) (83.96 KB, image/png)
2013-09-12 00:48 EDT, Aiko
no flags Details

  None (edit)
Description Aiko 2013-09-12 00:45:49 EDT
Filed from caserun (INSERT URL HERE)

Version-Release number of selected component (if applicable):

Steps to Reproduce: 

1. Move cursor over the Administer menu at the top right corner and click on

2. Click on the name of the required role from the left NAME panel.
    Information about the permissions and users assigned to this role is
    displayed on the right.
3. Click on Permissions. 
4. Click on + Add Permission.
5. Click Next without selecting any permission in the step 4.
6. The following error messages appear.

Validation Failed:

    Name can't be blank
    Name must contain at least 1 character

Actual results: 

The string "Name" which is part of the error message is left in English.

Expected results:
"Name" should be localized to "名前" and "名前は"
The whole message should look like below:


   名前は少なくとも 1 文字以上にしてください

Please see the attached screenshot for details.
Comment 1 Aiko 2013-09-12 00:48:54 EDT
Created attachment 796615 [details]
Unlocalized "Name" (English and Japanese)
Comment 2 Bryan Kearney 2013-12-02 15:45:05 EST
The move to Foreman and the new UI invalidates all previous localization testing. We will need to do a full pass through the UI again.

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