Editorial: Note on use of CLDR data for rounding currency values #921
Conversation
implementations using CLDR should not use CLDR's "cashDigits" and "cashRounding" attributes when formatting currency values.
ben-allen
force-pushed
the
cash-rounding-note
branch
from
95ee2c8
to
d2d2ab0
Compare
|
The current spec text doesn't even allow to use CLDR in the first place, because it explicitly references the "ISO 4217 currency and funds code list". I think we first need to a normative change to either allow in CLDR in addition to ISO 4217 or alternatively use CLDR instead of ISO 4217. IIRC it depends on the specific application if ISO 4217 or CLDR is a better choice. And for some applications neither is actually the best choice. |
|
Replaces #839 |
|
Does CLDR endeavor to match ISO-4217? Or are the CLDR currency digit settings just different from the ISO ones? Based on #134, it seems like it is expected for CLDR to differ. It would be nice to mention this in UTS 35, and then this PR should simply make it conformant for implementations to use something other than ISO-4217 digit counts. It should be an ILD behavior. |
This PR allows for locale data other than ISO 4217 for determining the number of fractional digits to be used when formatting currency values. In some applications ISO 4217 is most appropriate, in some CLDR data, and in some neither is best. See tc39#921 (comment) Resolves tc39#134 This PR makes the `CurrencyDigits` AO implementation-defined.
This PR allows for locale data other than ISO 4217 for determining the number of fractional digits to be used when formatting currency values. In some applications ISO 4217 is most appropriate, in some CLDR data, and in some neither is best. See tc39#921 (comment) Resolves tc39#134 This PR makes the `CurrencyDigits` AO implementation-defined.
|
Closed because replaced by #922, which makes the currency list used purely implementation-defined. |
* Normative: Allow use of non-ISO 4217 data in `CurrencyDigits` AO This PR allows for locale data other than ISO 4217 for determining the number of fractional digits to be used when formatting currency values. In some applications ISO 4217 is most appropriate, in some CLDR data, and in some neither is best. See #921 (comment) Resolves #134 This PR makes the `CurrencyDigits` AO implementation-defined. Co-authored-by: Richard Gibson <[email protected]>
For some currencies, CLDR gives two values for determining the number of minor digits displayed when formatting those currencies. This note explains that the value of the "cashDigits" attribute, and likewise the value of the "cashRounding" attribute, should not be used when formatting values denominated in those currencies.
fix #835 (or at least, close it).
address #134