Template talk:To USD round

Category for invalid value
Probably a single category should be used for this template, as well as Template:To USD, in the case of an invalid param value passed to either of them. I see no reason for each to have their own category. Mathglot (talk) 11:15, 13 December 2019 (UTC)
 * Changed per this discussion&#91;perma&#93; at WT:CATP. Mathglot (talk) 17:09, 14 December 2019 (UTC) edited; Mathglot (talk) 19:30, 25 June 2023 (UTC)

Add 'current' option
Conversions are to USD of the given year, but often one might want to know the amount in current USD. I think we should add new param yes which would do the conversion into current USD amount, by multiplying the original conversion by the ratio of USD now (or latest year available) to USD in the given year. Mathglot (talk) 19:34, 25 June 2023 (UTC)
 * Maybe not 'current' because the abbreviation 'cur' is used for 'currency' and could lead to confusion. Perhaps 'now' or 'latest' or something. Mathglot (talk) 19:43, 25 June 2023 (UTC)

Country Code Instead of Currency Code?
Why does this template use country codes to refer to currencies, when there are already three letter currency codes in common use for all current, and past, currencies (e.g. USD, EUR, FRF).

It seems quite counter-intuitive that we have to invoke ISO 3166-1 country codes, when there is not a 1-to-1 correspondence between them, and currencies (some countries share currencies, some countries have or have had multiple currencies, etc.), whereas ISO 4217 currency codes are standardised and do have a 1-to-1 relationship with currencies.

I don't want to start poking around and breaking things, so I'm leaving this note instead, perhaps someone has some information I lack. --Tomatoswoop (talk) 02:30, 28 August 2023 (UTC)

update: I see that this (and other similar templates) have an optional additional "cur" parameter to workaround this for Eurozone countries (so you would put in the country code and the currency code in that instance). This seems like a bit of an unnecessary kludge to me, surely we should just be using currency codes from the get-go? --Tomatoswoop (talk) 02:37, 28 August 2023 (UTC)