Bug 2083618 - [L10n][ja_JP][SAT_6.11] Wrong translations of the string present on page.
Summary: [L10n][ja_JP][SAT_6.11] Wrong translations of the string present on page.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Localization and Internationalization
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-10 12:45 UTC by visawant
Modified: 2023-07-21 23:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19107 0 None None None 2023-07-21 23:18:13 UTC

Description visawant 2022-05-10 12:45:29 UTC
Description of problem: On present build of satellite i.e 6.11.0 Beta, few pages have wrong translations available on page.


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


How reproducible: Always


Steps to Reproduce:
1. Login to Satellite 6.11 instance with zh_CN locale.
2. Navigate to below page locations given in "Additional info" section to look for wrong translations

Actual results: mistranslation of strings available on page.


Expected results: Localized strings should be translate correctly.


Additional info: Navigate to below locations.

1 Navigate to Administer - Authentication Sources page:
  1.1 Click on any item under Name column to Edit LDAP, click on tab "Attribute mappings", Mistranslation for "Attribute mappings"
  1.2 Again, Click "LDAP Server" then click "Submit" without setting Server type, Mistranslation for "Is not in the list." --> "とは一覧にありません。"

2 Navigate to Hosts - Job Templates:
  2.1 Click "New Job Template", Mistranslation "仕事" for "Job"
  2.2 Click Submit button, Mistranslation "を入力してください。" for "can't be blank".
  2.3 Check for Job Templates table list, click "Unlock" from "Actions" selection, Mistranslation "場所" for "location"

3 Navigate to Monitor - Host Statuses:
  3.1 Mistranslation "所有者" for "Owned"

4 Navigate to Administer - Users page:
  4.1 click "Impersonate" from dropdown Action, Mistranslation for "管理者から要求してください"

5 Navigate to Monitor - Audits:
  5.1 Click on Expand (> icon), Mistranslation for "UUID の要求"

6 Navigate to Administer - About page:
  6.1 Click on tab "Available Provider", Mistranslation for "をインストールか"

7 Navigate to Monitor - Report Templates:
  7.1 Click "Create Template", click tab "Inputs", then click on information icon, Mistranslation for "プレーン値のタイプ"
  7.2 Click "Create Template", click tab "Help", then scroll down and click (>) button of "Inputs" section, Mistranslation for "引数として 入力名をパスします"

8 Navigate to Configure - Host Group:
  8.1 create new host group, Mistranslation for "名前スペースを含めることはできません。と値hash は無効です"

9 Navigate to Hosts - Installation Media:
  9.1 Click on 'Create Medium', Mistranslation for "Medium"

10 Navigate to Hosts - All Hosts:
  10.1 Click on "clone" from action dropdown, Mistranslation for "を入力してください。と"
  10.2 Click on any hosts, Mistranslation for "を作成済み"

11 Navigate to Infrastructure - Subnets:
  11.1 Click on "Create Subnet", go to tab "Capsule", Mistranslation "プロキシー" for "Capsule"

12 Navigate to Configure - Discovery Rules:
  12.1 Click on "Create Rule", under tab primary click on Submit button, Mistranslation "を入力してください。" for "can't be blank"
  12.2 Action: Click on "Disable", Mistranslation "無効化されたルール" for "Rule disabled"
       Action: Click on "Enable", Mistranslation "有効化されたルール" for "Rule enabled"
       Action: Click on "Clone", Mistranslation "のクローン作成" for "Clone"

13 Navigate to Hosts - Policies:
  13.1 Mistranslation "平日" for "weekday"

Comment 8 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


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