Translations with \n are not translatable

[DanieliMi]

Preconditions and environment

• 2.4.6-p6
• A store with language de_DE
• The following in the translation file for de_DE:

  "Failed address validation:\n%1","Adressvalidierung fehlgeschlagen:\n%1"

Steps to reproduce

1. Go to storefront
2. Add a product to the cart
3. Go to the checkout
4. Fill in form
5. Provide an incorrect email address (for example just a string)
6. Ignore/circumvent JS validation (this testcase assumes frontend validation fails/does not work and we have to rely on the backend validation)
7. Place order

Expected result

You receive the translated message "Adressvalidierung fehlgeschlagen:..."

Actual result

You receive the original message. "Failed address validation:...".

Additional information

In https://github.com/magento/magento2/blob/1b99b6d59b27613ca70e60f4067743d715c3e02d/app/code/Magento/Quote/Model/SubmitQuoteValidator.php#L69C24-L69C56 "\n" is used but when the csv is read it equals to '\n' so the key cannot be found within \Magento\Framework\Phrase\Renderer\Translate::render.

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[bot]]

Hi @DanieliMi. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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. :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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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

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

@magento give me 2.4-develop instance

[engcom-Delta]

Hi @DanieliMi ,

Thanks for your reporting and collaboration. We have verified the issue in latest 2.4-develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce.

1. Store with language de_DE
2. Go to storefront
3. Add an item to cart
4. Navigate to checkout
5. Disable email field validation by changing the validation.js and elements Email Address field validation.js
6. Enter string value in the email field
7. Fill Shipping information and click on proceed/further button.
8. User will be navigated to the payment page.
9. Fill in payment details and click on place order button
10. Observe "Invalid Email Format" error displays instead of the error message mentioned in your steps i.e. "Failed address validation:..."

Please let us know if any other steps are needed to be performed.

Thanks.

[engcom-Delta]

Hi @DanieliMi ,

We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.