Open reshadzazai opened 3 years ago
Hi @reshadzazai. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: 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.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
This issue is there since 2.3 and most enterprise users are US based so no one cares :)
Hi @engcom-Bravo. 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: :point_down:
[ ] 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
branchDetails
- 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.
:white_check_mark: Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-40062
were created
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
There is an update for this issue:
Magento team is working on this issue. Here is the result of the investigation, the quote from MC-40062
The letters in Arabic language can be written slightly different depending on their position in the word which may lead to such situations if is not implemented correctly. It is not Magento issue as Magento uses external library for PDF creation.
According to developer's investigation:
We are using the Zend_Pdf library to work with pdf files. And it doesn't fully support RTL languages. We cannot fix this problem quickly, as it is necessary to either fix the Zend_Pdf library itself or change the logic to use another library, which will take a lot of time.
When the fix will be ready and delivered, this ticket will by updated by bot with commits
Is there any update?
any updates?
Any fixes on this?
Any fix for this ?
Any updates?
@magento I am working on this
@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://0ea68d0225b938ac589990eadb862785.instances-prod.magento-community.engineering Admin access: https://0ea68d0225b938ac589990eadb862785.instances-prod.magento-community.engineering/admin_9f03 Login: 87bfd85b Password: e9a38362c099
Hi @reshadzazai,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.
Steps to reproduce:
The characters are separated from each other in the PDF generated.
Hence Confirming the issue.
Thanks.
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-797
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-797
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-797
Description:
Summary of the issue: Arabic characters are separated in PDFs generated by Magento 2.4.1
Preconditions:
Information on your environment: Magento 2.4.1 Fresh Installation Also reproducible on 2.4-develop
Steps to reproduce:
While placing the order write the name and address information in Arabic and then process the order and print the invoice PDF.
Expected results:
The details have to be shown the way displayed in the admin panel while looking at the invoice.
Actual results: The characters are separated from each other in the PDF generated.
Additional info from Engcom
Please see the related issue reported previously https://github.com/magento/magento2/issues/25769 Steps to reproduce 1) Place an order in Arabic store 2) Customer fill the address and name all in Arabic 3) Login to the admin panel and open orders 4) Create an invoice against the order 5) Download the invoice pdf and compare the content in the admin side with the invoice pdf