Tom Bishop

The second commit removes the code changes involving "blank" values

Please note that the ticket is still "investigate", and this PR is intended to illustrate possibilities rather than a final design. Screenshots are based on running ST locally with these...

So far (commits 1 and 2) this PR only supports the conventional U+... notation (plus character names) to help identify characters. A likely enhancement would be to add support for...

> The package I pointed to seems to do all of this, based on their demo. I tried the Tagify demo some more (specifically "Mix text & tags"), and I...

@srl295 The ticket is now accepted and this PR is ready for review; substantive changes depend on DEBUG = true and Shift-clicking on Cancel button for now. It would be...

 LGTM. The ticket isn't accepted yet, though. I'm curious, how is this data used?

@conradarcturus FYI, I see that a PR of mine, with changes to languageGroup.xml among others, was merged back in March 2024: https://github.com/unicode-org/cldr/pull/3538 I don't remember whether those changes were made...

Actually, looking at https://github.com/unicode-org/cldr/pull/3538 I see that I wrote there about hand-editing likelySubtags.xml in discussion with @macchiati -- and GenerateMaximalLocales is disabled, not to be confused with GenerateLanguageContainment...

> do you know which is the right adaptation that can run this script from code-rdf (side-question, why is it in cldr-rdf and not cldr-tools?). This seems to work for...

LGTM but I don't see what this has to do with the ticket https://unicode-org.atlassian.net/browse/CLDR-14139