This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2083526 - [L10n][zh_CN][SAT_6.11] Localization issue - Wrong translation of strings on "Administer - Locations page"
Summary: [L10n][zh_CN][SAT_6.11] Localization issue - Wrong translation of strings on ...
Keywords:
Status: CLOSED MIGRATED
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 09:43 UTC by visawant
Modified: 2024-06-06 12:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:21:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Wrong translation of string (27.08 KB, image/png)
2022-05-10 09:43 UTC, visawant 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-16388 0 None Migrated None 2024-06-06 12:21:17 UTC

Description visawant 2022-05-10 09:43:38 UTC 
Created attachment 1878275 [details]
Wrong translation of string

Created attachment 1878275 [details]
Wrong translation of string

Description of problem: Incorrect translation present for Chinese language.


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. Click on "New Location" button, 
3. Translation for Taxonomy is not correct

Actual results: Incorrect translation for word


Expected results:
Translation of the source string "Taxonomy|Name" should be corrected from "Taxonomy|名称" to "名称"
Translation of the source string "Parent" should be corrected from "亲" to "父"


Additional info: Please see attached screenshot
Comment 4 Adam Ruzicka 2023-05-19 12:34:11 UTC 
I'm not sure what we're supposed to do here. Yes, we can pull updated translations, but we have no idea if it's actually fixed there.

As of stream snap 14, the used character is different than what is shown in screenshot mentioned in #0. The character that is there now is 父 which from my limited knowledge is just "father". Is that we should be there?
Comment 8 Ludek Janda 2023-06-01 07:47:25 UTC 
(In reply to Adam Ruzicka from comment #4)
> I'm not sure what we're supposed to do here. Yes, we can pull updated
> translations, but we have no idea if it's actually fixed there.
> 
> As of stream snap 14, the used character is different than what is shown in
> screenshot mentioned in #0. The character that is there now is 父 which from
> my limited knowledge is just "father". Is that we should be there?

According to our Chinese language specialist and reporter of this bug,  the word 父" is means "Parent" and is correct in this context. I have checked out the latest - 6.14 project in Phrase and this word is correctly translated there.
Comment 10 Adam Ruzicka 2023-06-02 12:27:22 UTC 
Thank you. Then we can go straight back to new, the original issue with parent is fixed, but not the one with taxonomy.
Comment 11 Adam Ruzicka 2023-06-05 07:47:52 UTC 
Considering the scope changed last thursday, I don't think we can go through the whole transifex->upstream->downstream loop in time
Comment 13 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 14 Adam Ruzicka 2024-01-05 10:23:52 UTC 
On 6.15.0 snap 4, "Taxonomy|Name" is still "Taxonomy|名称" instead of expected "名称".
Comment 16 Adam Ruzicka 2024-01-11 10:53:03 UTC 
Flipping components to have this resolved in the translations
Comment 19 Eric Helms 2024-06-06 12:21:19 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.