Integrate LocaleDistanceBuilder into CLDR-to-ICU tooling and run with non-staging data.
As this is part of the LDML data build step, it makes sense to integrate it into the new tool chain and use the CLDR API for data access.
However, it's also a tool which should be runnable stand-alone during debugging and development, so should probably be made available in both contexts.
In fact, all supplemental data processing (where no "//ldml/" paths are needed) should probably be made available to be run without requiring "productionised" staging data, since (I believe) that staging data only affects //ldml/ paths.
This works now (the new converter is in and you can run it on non-staging data without any issues).
It works if you just point the CLDR_DIR at non-staging data providing you don’t attempt to convert locale data.
Sounds good. It would also be useful to be able to run the converter on raw CLDR locale data, especially where I would expect the staging version to be the same, as for collation.
(I might be wrong that for collation raw==staging. At least I am sure that collation data has no no-inheritance markers to be removed.)