This is not a bug.
You can change the Currency display settings in "Stores > Currency > Currency Symbols"
@IlnitskiyArtem You can set there only symbol. I.e. if you would like to show CHF price in store view with fr_FR language price will show as 99.99 CHF, and it doesn't matter that country is still set to Switzerland. So I don't think it is the good place to change this.
Tell me if I'm wrong.
@IlnitskiyArtem what is more, in i.e. de_DE store view currency is already displayed as CHF 99.99, so with additional space it looks like this:

@Bartlomiejsz, Thanks for the feedback.
We've created internal ticket MAGETWO-70275 to address this issue.
@Bartlomiejsz, thank you for your report.
We've created internal ticket(s) MAGETWO-70275 to track progress on the issue.
Hi @Bartlomiejsz
This ticket has been marked as "Triage Wanted" due to low user involvement over time. Over the next 2 weeks we are looking for additional community feedback to decide if it should be archived or not. More information on this is available on the GitHub wiki.
Thank you for collaboration.
@magento-engcom-team Should not-solved issue be closed after two weeks? Really?
Hi @Bartlomiejsz
This is not the idea behind this. Intent is to close only inactive issues.
We have wrong currency symbol for Singapore Dollar. It always shows "$" instead of SGD, S$ or the user entered value in the backend.
Note we have a multi-store setup, with at least 10 currencies. Singapore Dollar is the only wrong format.
Even CHF is shown correctly.
How is the progress on this one?
@johnny-longneck I've replicated the issue on version 2.2.8. The issue seems to be caused by the zend framework library that is being used that causes the "$" symbol to be used by SGD currency.
Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.
Please feel free to comment or reopen according to the Issue reporting guidelines
the ticket if you are still facing this issue on the latest 2.x-develop branch. Thank you for collaboration.
Too bad this was closed. We are having the same issue with singapore dollars too.
@avoelkl @johnny-longneck @olivercastro
Similar issue with Canadian Dollar we were fixing by setting en_CA locale for store. In your case you should probably define locale en_SG
Reopened this issue to re-consider, investigate one more times
@engcom-Golf Could you please have a look and investigate it?
Hi @sdzhepa. 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:
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 branchDetails
- 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.
Hi @engcom-Golf. 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:
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 branchDetails
- 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.
Hi @avoelkl @olivercastro, thank you for attention on this issue, the current behavior is correct, for now magento render prices depend on locale that your store have, for example if your store have en_US locale and you have for example CHF currency, then all curency will be displayed as an "USA standart prices" not an "CHF".
And If you switch locale to de-CH then your price will render for Swiss standards.
If we will decide to change this behavior and render prices by their own standarts, wich mean every currency will be rendered per standard wich uses for their country, it may breaks a lot of thirth party extensions, and this changes also must be reviewed and approved by Product Owner, but i'm not sure that this behavior will be correct, so i think current behavior of rendreing prices is correct.
This, thanks for having a look again.
I'll talk to my colleague if the he set en_SG correctly. @ihor-sviziev
Most helpful comment
Hi @avoelkl @olivercastro, thank you for attention on this issue, the current behavior is correct, for now magento render prices depend on locale that your store have, for example if your store have en_US locale and you have for example CHF currency, then all curency will be displayed as an "USA standart prices" not an "CHF".
And If you switch locale to de-CH then your price will render for Swiss standards.
If we will decide to change this behavior and render prices by their own standarts, wich mean every currency will be rendered per standard wich uses for their country, it may breaks a lot of thirth party extensions, and this changes also must be reviewed and approved by Product Owner, but i'm not sure that this behavior will be correct, so i think current behavior of rendreing prices is correct.