Translation issue in admin grid on different locales

[mobeen-sarwar]

Preconditions (*)

1- Magento 2.3.4-p2
2- Magento 2.3.5-p2
3- Translations for at least two locales

Assumptions(*)
1- We are assuming that we have three locales English, Japanese, and Korean, with translations.

2- Make sure we have added translations for this path Admin->Sales->Orders->view(open an order details)->Transactions

Steps to reproduce (*)

1- Login to Magento admin
2- Go to this path Admin->Sales->Orders->view(open an order details)->Transactions and note down header translations

3- Now set the Interface Locale to Korean assuming the previous was English US (Go to admin -> Account Settings).
4- Repeat step 2.

Expected result (*)
1- Grid headers should be translated into Korean.

Actual result (*)
1- Grid headers are still in English.

[m2-assistant]

Hi @mobeen-sarwar. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[mobeen-sarwar]

@ajijshekh123

[m2-assistant]

Hi @engcom-Alfa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Alfa]

Hi @mobeen-sarwar .

Unfortunatelly, we are not able to reproduce this issue on fresh 2.4-develop.
Everything works as expected.

Actual Result:

✔️ Japanese Language

✔️ Korean Language

So, we have to close it.
Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch. Thank you for collaboration.

[mobeen-sarwar]

Hi @engcom-Alfa

Thanks for your humble responce. I already checked it on Magento 2.4 and found no issue there. I'm facing this issue on Magento 2.3.4-p2 and Magento 2.3.5-p2. So I'm looking a fix for Magento 2.3.4-p2 version.

Many thanks for your instant response.