I don’t want to hard-code foreign currencies into the program. I only hardcode immutable concepts which will be true today and 100 years from now.
Also, it’s not just about having list of all foreign currencies. When Manager is used in non-English language, foreign currencies need to reflect that too - so that’s another complication. Not to mention, localization shouldn’t have all the foreign currencies, just 5 or 10 which are the most common for given country. If you are adding Belize dollar to Indian localization, that’s not justified. But it would be justified in Mexcian localization.
I am not saying you should hard-code the foreign currencies. I guess my explanation could have been better.
What I suggested was some method to share data between the individual localizations, currencies in this case. Sourcing the foreign currencies from base currencies of other localizations would be beneficial because those base currencies would be entered by a user who knows the local laws better.
So every user would have as many pre-verified foreign currencies as the number of localizations. Users can always add any other foreign currency to their local data file to meet their individual requirements.
I know what you mean. You want to reduce inefficiencies and duplication. But your solution where currencies are shared across localizations will solve one set of problems but introduce new set of problems.
First of all, no currency is called the same around the world. Sure, for Canadians or Indians, it is US Dollar but for French it is Dollar américain, for Dutch, it is Amerikaanse dollar. You get the idea.
Then you have symbols. For example, $ symbol in India would typically refer to US Dollar but in many countries with dollar-based currency, $ symbol is used for base currency and US Dollar is shown as US$.
Not to mention, I do not want localizations to contain all foreign currencies - just most common in given country. It should serve as a starting point. Not final solution which when it comes to currencies - nothing is final.
so considering below screenshot as an example, the foreign currencies should also be in the base language. and symbols should be distinct, for example, US$ and AU$. @ASEGC1725 please check.
@Omnipotent.inc decimal places refer to the smallest monetary unit. If you leave US dollar at 4 decimals, all invoices will show 25.0000 USD instead of 25.00 USD. Maybe for some businesses it’s desirable but for vast majority it’s not.
@lubos why not implement the Foreign Currencies form which conforms to the ISO 4217 standards? the user could select a country and the corresponding currency would be shown.
agreed. so in my opinion maybe we could simply import whichever currencies are defined in the ISO standard and let the user edit them to their needs and also create non standard currencies. would this be okay since these currencies will be anyway set inactive by default?
I prefer if only common currencies were created though. Not all of them. For example, I doubt you can open bank account in India that will hold Solomon Islands dollars for example. So no point adding this foreign currency in Indian localization because it won’t be used by almost anyone there. Only important foreign currencies in India should be added.
