Some currency doesn't correct about countries

[Omranic]

Yes, I agree. We may have to change getCurrency behavior and omit or separate the details currencies into different attribute for all countries. I'll keep this issue opened until further review.

[Omranic]

@khsing Check this please & tell me what do you think http://forexesteem.blogspot.com.eg/2009/03/explanation-of-usdussusn.html

[khsing]

@Omranic In general the currency of USA is USD, although USN and USS are more detailed currency code, but not normal.

I think getCurrency should return the Currency which people used to use.

[willemwollebrants]

I had the same problem. I've fixed it by adding an optional key 'default_currency' to the country data, and a new Country::getDefaultCurrency method. If default_currency is not set, Country::getDefaultCurrency returns the same as Country::getCurrency. (I could have just altered the order of currencies in the json files, but explicitly defining it seems more secure)

My code's here, if it's ok I can send a PR for this

[markitosgv]

+1 for USD instead of USN

[Omranic]

Thank you for your patience, this is now fixed fundamentaly for all countries in 1cf372b, here's what's been done:

Update country currencies to include only the official currency (fix #52 #55 #72)

• Removed fund, complementary and secondary currencies as it's not relevant to the countries package, and caused confusion before
• This change affected 15 countries: Bolivia, Bhutan, Belarus, Switzerland, Chile, Cuba, Western Sahara, Haiti, British Indian Ocean Territory, Lesotho, Namibia, Panama, El Salvador, United States, Uruguay