Filipino (philippines) language translation not working!

[pawan]

Preconditions (*)

1. Magento 2.3, 2.4, 2.4-develop
2. Multi Store

Steps to reproduce (*)

• Create a new store view for philippines i.e. philippines

• Go to system -> configuration -> change scope from Default to philippines store view

• Change locale to Filipino (Philippines)

• Install language pack for Filipino i.e. composer require mageplaza/magento-2-filipino-language-pack:dev-master Or can create a custom language pack

• Go to front-end and change Store view form Default to Philippines

Expected result (*)

1. translation should work on frontend!

Actual result (*)

exception(s):
Exception #0 (Magento\Framework\Exception\LocalizedException): The XML in file "/vendor/mageplaza/magento-2-filipino-language-pack/language.xml" is invalid:
Element 'code': [facet 'pattern'] The value 'fil_PH' is not accepted by the pattern '[a-z]{2}([a-zA-Z]{4})?[A-Z]{2}'.
Line: 3

Verify the XML and try again.
Exception #1 (Magento\Framework\Config\Dom\ValidationException): Element 'code': [facet 'pattern'] The value 'fil_PH' is not accepted by the pattern '[a-z]{2}([a-zA-Z]{4})?[A-Z]{2}'.
Line: 3

Exception #0 (Magento\Framework\Exception\LocalizedException): The XML in file "/var/www/html/m2-git/vendor/mageplaza/magento-2-filipino-language-pack/language.xml" is invalid:
Element 'code': [facet 'pattern'] The value 'fil_PH' is not accepted by the pattern '[a-z]{2}([a-zA-Z]{4})?[A-Z]{2}'.
Line: 3

Additional Information (*)

All other locale have code either az_AZ or az_aAzZ_ZZ, only Filipino language have code fil_PH which is different form all other codes.

---

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]

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

  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.

[Bashev]

@magento I am working on this

[m2-assistant]

Hi @Bashev! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[Bashev]

@magento add to contributors team

[m2-assistant]

Hi @Bashev! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[Bashev]

@magento I am working on this