Currency symbol for Danish Krone doesn't match what is shown in the backend.

[jupiterhs]

Preconditions (*)

1. Magento 2.4.0 (2.4-develop)

Steps to reproduce (*)

1. Set Locale to Danish (Denmark)
   
2. Set Base Currency and Default Display Currency to Danish Krone

Expected result (*)

1. Should display the currency symbol as DKK in the frontend as defined in the backends Currency Symbol section
   

Actual result (*)

1. Displays kr in the frontend instead of DKK
   

More Information

1. If we switch the Locale to English (United States) then it shows DKK in the frontend as expected.
   

Workaround

1. Put a space before the currency symbol in the backend.

What I have found

1. The kr comes form the file public_html/vendor/magento/zendframework1/library/Zend/Locale/Data/da.xml line 3668

---

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

[jupiterhs]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @jupiterhs. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @jupiterhs, here is your Magento Instance: https://d3f72cb5b008e9e7d6a304bc19c02018-2-4-develop.instances.magento-community.engineering
Admin access: https://d3f72cb5b008e9e7d6a304bc19c02018-2-4-develop.instances.magento-community.engineering/admin_2fdc
Login: 4193b868
Password: 8da68b7a0b5b

[m2-assistant]

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

[jupiterhs]

Hi I am able to reproduce this on the 2.4-develop instance

[engcom-Bravo]

Hello @jupiterhs

Thank you for your report

We have set the Interface Locale to Dansk (Danmark) / dansk (Danmark)

and set Base Currency and Default Display Currency to dansk krone

The products on the Storefront are displayed with DKK currency as described in the Expected Result

Can you please correct our steps?

Thank you in advance

[jupiterhs]

Hi @engcom-Bravo
Thanks for checking.

I have updated the issue.
You need to set the locale like below

[engcom-Bravo]

@jupiterhs Thank you for the quick response.

The Storefront is using the Currency Symbol specified in Stores - Currency Symbols

If you'll change the default ".kr" to "DKK", the symbol "DKK" will be displayed on the Storefront

[jupiterhs]

@engcom-Bravo
You are able to change it to DKK because you changed the Interface Local. Please try switching it back to English and you should see something like below and then you should be able to see the issue.

[jupiterhs]

Hi @engcom-Bravo
Hope you are having a good day :)
did you get a chance to check this out?

[engcom-Bravo]

Hello @jupiterhs

Sorry for the delay. We Confirm that the issue is reproducible on the latest 2.4-develop.
Thank you for updating the description, and for communication.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-41078 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[mortenbirkelund]

Still relevant

[4DallasC]

Howdy All,

Having the same problem with PHP v7.4 and not with PHP v7.3. Looks like a change to how PHP's \NumberFormatter::formatCurrency operates when the second parameter string $currency is provided. In v7.4 it now overrides the applied setting of the currency symbol with the default in PHP.

The following edit is required in \Magento\Directory\Model\Currency::formatCurrency(string $price, array $options): string:-

$formattedCurrency = $this->numberFormatter->formatCurrency(
   $price, $this->getCode() ?? $this->numberFormatter->getTextAttribute(\NumberFormatter::CURRENCY_CODE)
);

to:-

$formattedCurrency = $this->numberFormatter->format($price);

[bobemoe]

Having same issue, 2.4.4CE

The workaround specified in OP ("Put a space before the currency symbol in the backend.") works fine for me.

The code change in post directly above does not make any difference for me.