-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2022-06-15] $500 If your have your language set to Spanish, the currency is not localized when you select it #7915
Comments
Triggered auto assignment to @robertjchen ( |
Great catch, opening this up for a contributor to tackle! 👍 |
Triggered auto assignment to @laurenreidexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Triggered auto assignment to @tgolen ( |
@iwiznia Do you think we have to update this page as well? |
Good question, I think yes we probably should. |
I guess this is still waiting for proposals. |
@tgolen This is better to solve in the API Backend. I can't be sure whether the data is in the database or hardcoded data in Backend. The reasons why it should be backend,
Although I can propose a workaround in App to force adding the |
Thanks @cylim! Ideally, it should work like this:
Just for reference, the currency info from @iwiznia It appears to me that we are formatting the currency correctly. The OP says you are expecting to see |
User-selected Spanish locale and for them, $ should be shown as US$. This is part of localization and thus it can be handled on UI. -- Update grammer |
@tgolen
These are not standard symbols too. Another suggestion is not to use the $,£,¥ symbols, directly using USD, SGD or AUD in the IOU screen. (frontend fix-able) My proposal is,
And if we want to translate it, we can translate the @parasharrajat |
Not sure if international, but yes, some countries were their currency is not USD use US$ to indicate amounts in USD.
No, I don't think we should update that because all the other systems using it, will break. The main problem with that file is that it is not internationalization aware, it assumes everyone is in the USA. All symbols there are how the USA represents the currencies, not how every country does it. Our new localization methods in newDot are internationalization aware and can take a currency code (the keys in the array you linked) and transform it to an amount using a specific locale. So for example USD 1000.23 in the USA would be shown as |
📣 @mdneyazahmad You have been assigned to this job by @laurenreidexpensify! |
@laurenreidexpensify applied |
Upwork was being a bit weird about allowing me to update this to $500, so ignore what it says there but @mdneyazahmad @parasharrajat I will make sure appropriate payment is issued after deploy. |
Update: PR is ready will create soon. |
This issue has not been updated in over 15 days. @tgolen, @parasharrajat, @laurenreidexpensify, @mdneyazahmad eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Look like we're still making steady progress as per the PR |
This issue has not been updated in over 15 days. @tgolen, @parasharrajat, @laurenreidexpensify, @mdneyazahmad eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@parasharrajat @mdneyazahmad what's the latest here on the PR ? Who are we waiting on to take the next action: contributor, contributor plus or Expensify engineer? |
@laurenreidexpensify waiting review from @tgolen |
Merged, let's hope everything will go smooth 🎉 Great work @mdneyazahmad |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.73-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-06-15. 🎊 |
Everyone has been paid. Hurrah 4 months later and we're finally done :) Well done everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Currency should be localized
Actual Result:
Currency is not localized.
It should be. ie: if I select USD, the symbol shown should be US$ and not just $.
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.40-0


Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @iwiznia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1645483634039679
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: