i18n:collect-phrases does not include titles in layout files

[norgeindian]

Preconditions (*)

1.2.4.3-p2

Steps to reproduce (*)

1. Take a look at Magento_Customer/layout/override/base/customer_account_create.xml. You will find the following line: <title>Create New Customer Account</title>
2. Run bin/magento i18n:collect-phrases --output=test.csv vendor/magento/module-customer/view/frontend/layout/

Expected result (*)

1. I would expect, that the title "Create New Customer Account" would be included in the test.csv file, as given translations for titles actually wor.

Actual result (*)

1. The phrase is not included in the exported file.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] 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.
• [x ] 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 @norgeindian. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

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.

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

[m2-assistant[bot]]

Hi @engcom-Hotel. 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 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-Hotel]

Hello @norgeindian,

Thanks for the report and collaboration!

We have tried to reproduce the issue in Magento 2.4-develop branch and the issue is reproducible for us. But I would like to suggest you a workaround to translate the title text here.

I request you to please go through with this link, it might resolve your issue.

Or if you have any other use case and you need the text in the CSV file then please let us know.

Thanks

[schizek]

I am reproducing the same issue on 2.4.4 of Adobe Commerce. We need to provide translation files to our translators with all phrases as opposed to manually poking around after things have been translated and finding all these missed phrases. It would be highly beneficial to include these within the output of i18n:collect-phrases.

[norgeindian]

@engcom-Hotel , thanks for the idea, but I'm totally with @schizek . This command should offer the possibility to make sure,that definitely all phrases, which must be translated, are included. Currently, all automatically created language packs are missing these parts. In the Devdocs, the following is written down:

To begin translating, use a command to generate a dictionary .csv file with a collected list of all existing phrases and words.

So this should be definitely fixed in my eyes, so that these phrases are included as well.

[engcom-Hotel]

Hello @norgeindian,

Thanks for the feedback!

I am confirming this issue for further process.

Thanks

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-3226 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Hotel]

Hello @norgeindian,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-3226 by the internal team Related commits: https://github.com/magento/magento2/search?q=AC-3226&type=commits

Based on the Jira ticket, the target version is 2.4.6.

Thanks