Han-Latin-Names.json should have alias Han-Latin-Names, currently it just has source (Han) and target (Latin), and the alias derived from that clashes with Han-Latin.json
am-Ethi-t-d0-morse.xml uses unescaped $ in Unicode set, this is not compatible with the variable semantics introduced in CLDR-16811
byn-Ethi-t-byn-latn-m0-xaleget.xml does not currently parse in ICU4X, the error messages is an invalid back reference. Need to investigate
Han-Spacedhan.xml defines a variable as a sequence of two Unicode sets, when probably a union is intended. This doesn't currently parse in ICU4X, and is therefore probably incompatible with the semantics introduced in CLDR-16811
Multiple transliterators use non-canonical property casing, which ICU4X does not support
[:script=foo:] instead of [:Script=foo:] or [:sc=foo:]
CLDR issues
Han-Latin-Names.json should have alias
Han-Latin-Names
, currently it just has source (Han
) and target (Latin
), and the alias derived from that clashes withHan-Latin.json
de-ASCII.xml refers to a
Any-ASCII
transform, which is not defined in CLDR or UTS-35. This issue was raised on the original ticket: CLDR-10092Thai-Latin.xml refers to a
Any-BreakInternal
transform, which is not defined in CLDR or UTS-35und-Ethi-t-und-latn-m0-beta_metsehaf-geminate.xml refers to a
Ethiopic-Latin/BetaMetsehaf
transform which is not defined.am-Ethi-t-d0-morse.xml uses unescaped
$
in Unicode set, this is not compatible with the variable semantics introduced in CLDR-16811byn-Ethi-t-byn-latn-m0-xaleget.xml does not currently parse in ICU4X, the error messages is an invalid back reference. Need to investigate
Han-Spacedhan.xml defines a variable as a sequence of two Unicode sets, when probably a union is intended. This doesn't currently parse in ICU4X, and is therefore probably incompatible with the semantics introduced in CLDR-16811
Multiple transliterators use non-canonical property casing, which ICU4X does not support
[:script=foo:]
instead of[:Script=foo:]
or[:sc=foo:]
[:ideographic:]
instead of[:Ideographic:]
[:case-ignorable:]
instead of[:Case_Ignorable:]
Filed CLDR-18043 for the rest