Email lang unclear

[vandijkstef]

Preconditions and environment

• Mage version irrelevant - but still present in 2.4.8

Steps to reproduce

Send an (HTML) email towards gmail users with potential mixed language.

In our case we send out an email in Dutch language containing the word "Wit" (EN: White) which got taken as 'Wit' (EN: Wit) which got replaced with "Geestigheid" (EN: Wit)

Expected result

The email showing as intended

Actual result

Lately we have been getting some reports from customers that had weird data show up in their order confirmation (html email). All these users turned out to be Gmail users, and their software is prone to automatically translate emails. So, while I'd like to call this an 'user issue' I dove a little deeper: Mainly the email templates (email/header.html) are NOT decorated with a 'lang' attribute. Some email clients might wrongly assume the email is not in the users native language and will attempt to translate these fields, leading to confusing customers.

Additional information

I am suggesting to add a 'lang' attribute to HTML email templates, as recommended by W3 for any HTML document.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @vandijkstef. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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, join the Community Contributions Triage session to discuss the appropriate ticket.

[hostep]

@vandijkstef: it may make sense indeed. Can you confirm if adding a lang attribute actually solves the issue? Or is that just a guess? If it's just a guess, I suggest we first try to find the proper fix and confirm it works before starting working on a fix for this.

[vandijkstef]

@hostep I have not confirmed this fix yet. I can probably tell more about that next week.

Pushing towards proper standards didn't seem like a bad idea anyway and possibly there are more people with a similar issue. I couldn't find anything related.

[m2-assistant]

Hi @engcom-Delta. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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-Delta]

Hi @vandijkstef ,

Thanks for your reporting and collaboration.
We have tried to reproduce the issue in 2.4.8 instance and we are not able to reproduce the issue.Kindly refer the attached screenshot.

Steps to reproduce :

1. Send an (HTML) email towards gmail users with potential mixed language.
   2.In our case we send out an email in Dutch language containing the word "Wit" (EN: White) which got taken as 'Wit' (EN: Wit) which got replaced with "Geestigheid" (EN: Wit)
   Before Translation

After Translation

Kindly recheck the issue in 2.4.8 instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[engcom-November]

Hello @vandijkstef ,

I wanted to follow up on the issue on the above commented on a couple of weeks ago.

#39857 (comment)

Please let me know if there's anything further needed from my side.

Best regards,

[m2-assistant]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[vandijkstef]

@engcom-November Sorry for the delay - 2.4.8 has some other side effects for us taking up my time.

My initial testing to put a lang attribute on the HTML-tag is NOT giving better results. It seems it's being completely ignored in gmail client.
I have moved the location of the attribute to test other locations - this goes along with my regular deployments to production so test loops take a little longer - but at least we're having real world examples.