-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store: Localize currency symbols #1547
Comments
If I'm not mistaken, #6046 solves a part of this. |
@lamosty not sure. As this is already using $ instead of USD and there are lots of countries using $ as their currency symbol from Liberia Dollar to Mexican Peso (Argentina, Chile...) More info here: http://www.xe.com/symbols.php |
Again, another example today with user cititsolutions reporting this should be clarified :) |
This came up in another support conversation, where a user in Brazil thought the displayed price was in BRL instead of USD. (Internal ref: 197408-h) Additional clarification about the $ sign referring to USD would help in these cases. |
I'm glad this has already been looked into. We'll have more confused users with Simple Payments that has just launched. |
I've just realised how old this issue is, and I wonder if it helps to tackle this issue bit by bit - making $ symbol always explicit including for US Dollar, that alone will go a long way. |
I merged a fix that helps a bit with some $ currencies #28380 Instead of "$" we now show "S$" for Singapore dollar etc:
This helps especially with Simple Payments which could have multiple payment buttons in different currencies on one page. |
Moved to Checkout Redesign for triaging. |
Currently prices for domains and other products are displayed with a currency symbol, such as $ or €:
In some countries, though, the $ sign is used for the local currency, for example for peso in Argentina. So displaying something like

can be confusing.
Therefore:
What might make the implementation of the fix trickier, is that for the displayed currency there is also a geographic component (for example with English display language but location in Europe, the Euro sign is being displayed).
The text was updated successfully, but these errors were encountered: