Magento URL Rewrites not support some characters (portuguese brazil)

[davirs]

Preconditions (*)

1. Magento version 2.3.5-p1
2. Have products/categories created with the Generate "category/product" URL Rewrites config set to Yes in Stores->Config->Catalog->SEO.

Steps to reproduce (*)

For categories:

1. Go to catalog>categories and add a new category.
2. Insert in Category Name: "Armação" or "Computação"
3. Leave Search Engine Optimization>URL Key blank
4. Save category

For products and images:

1. Go to catalog>produtcs and add a new product
2. At the product name set: "Armação" or "Computação"
3. At picture, upload a picture with same name of the product
4. Leave Search Engine Optimization>URL Key blank
5. All another parameter can be randon to gererate the product
6. Save the product

Expected result (*)

For categories:

1. Transform "Ç" into "C". Same thing for all portuguese brazil special characters for url rewrites.

For products and images:

1. Transform "Ç" into "C". Same thing for all portuguese brazil special characters at url rewrite and files names.

Actual result (*)

For categories:

1. [category panel backend]
   

2. [category page frontend]
   

For products:

1. [product page backend]
   
2. [product page frontend]
   
3. [product file renamed]
   

Important Notes:

• URL Rewrites in Magento 1 supports by default all portuguese brasil special characters.
• I have more than 3.000 products, it´s impossible set one by one manually.

---

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.
• 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 @davirs. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

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.

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

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[m2-assistant]

Hi @ajijshekh123. 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.

[ajijshekh123]

@magento give me 2.3.5-p1 instance

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.3.5-p1 instance for you

[magento-engcom-team]

Hi @ajijshekh123, here is your Magento instance.
Admin access: https://i-29444-2-3-5-p1.instances.magento-community.engineering/admin_c9f7
Login: fe3f5785 Password: dfb7e7f97477
Instance will be terminated in up to 3 hours.

[ajijshekh123]

Hi @davirs,
I have verified all Portuguese brazil special character's keyword in Magento 2.3.5-p1 instance.
I don't know this functionality is available in Magento 1 or not but this issue is reproduced in the Magento 2.3.5-p1 instance.
If this is not an issue so we can consider this issue as a Feature request.

PFA:

Thanks.