We're updating the issue view to help you get more done. 

In CLDR 30, "arab" number system lost currencySpacing, accounting currency formats

Description

Refiled from [#comment:37]

Because of the last diff in
http://unicode.org/cldr/trac/changeset/12636/trunk/common/main/root.xml for :, many Arabic locales no longer have currencySpacing
information or an accounting currency format (for the Arabic number
system). Is this intentional?

=> No, this was not intentional, due to replacing the alias with the explicit currency format without also copying all of the other stuff that would have been pulled in via the alias. This is a serious bug. <=

This caused two bugs in globalize.js:
https://github.com/jquery/globalize/issues/640 (more info:
http://stackoverflow.com/questions/40056378/bug-hunt-cldr-30-json-data-no-longer-has-currencyspacing-information)

From what I could tell, ICU4J deals with the missing currencySpacing by
using a hard-coded default (http://bugs.icu-project.org/trac/browser/icu4j/trunk/main/classes/core/src/com/ibm/icu/impl/CurrencyData.java#L86),
and it falls back to the latin number system's accounting format
(http://bugs.icu-project.org/trac/browser/icu4j/trunk/main/classes/core/src/com/ibm/icu/text/NumberFormat.java#L1497).
Is this correct?

Environment

None

xpath

None

locale

None

Status

Assignee

Peter Edberg

Reporter

Peter Edberg

Labels

None

tracReporter

pedberg

tracOwner

pedberg

tracResolution

fixed

tracStatus

closed

Reviewer

John Emmons

phase

final

tracCc

None

tracCreated

Oct 17, 2016, 5:06 PM

Components

Fix versions

Priority

critical