Tibetan and Dzongkha collation confirmation status

Only other remaining task on this task is to see if we can get an authority to confirm the Dzongkha collation.

It sounds like an ICU tooling problem, so a ticket should be filed there, so that we don’t generate an empty file if the data is not confirmed.

Copying July comment ( ) in readable format:

We're using ICU to implement the Intl.Collator object, and it seems like ICU is returning inconsistent data about the supported collation types. ICU claims it supports "dz" (per ucol_getAvailable), but when we construct the UCollator object, the actual locale is the root locale. (I still need to verify this for ICU4C, but at least that's the case for ICU4J.)

This bug can also reproduced for the locales "bo" (which imports the collation rules from "dz") and "wae", and also for the collation "de-u-co-eor" (per ucol_getKeywordValuesForLocale, "de" supports "eor", but the actual collator uses "und-u-co-eor").

"dz", "bo", "wae", and "de-u-co-eor" all have in common that their status is either draft="unconfirmed" or draft="provisional" ().

Yes, good point, it is really about the problem that we have a bundle whose contents are entirely unconfirmed. It is more like an error in the CLDR-to-ICU integration process, we should skip the collation bundle if it has no confirmed contents.

Thanks! In my mind this issue is not really related to Dzongkha or TIbetan, it’s really about what’s described in :