The fix for had issues, so was rolled back. Resurrecting it in this bug.
One part of the description of import on the following page was omitted in 1.9. It needs needs to be added to 2.0, before we add actual <import> statements.
That is the following:
Add private as an additional attribute for `<settings>`:
`<settings private="true"> // mirroring <transform>'s private attribute`
See , this should be 'visibility'
Moving all 25dsub and 25design tickets to 25rc. If you plan to complete items in the 25M1 time frame, please move those tickets to 25M1.
We should not (need to, have to) add "private" tailorings to bcp47/collation.xml.
CLDR meeting 2014-04-23: (some discussion bullets omitted here)
Markus proposes to distinguish for-import-only rules from create-a-sort-order rules via a naming convention rather than flags in the data
See email “CLDR/ICU proposal: collation rules for import only”
Proposal: First character in collation type == digit ‘0’ means for-import-only, e.g., “0kana”; no “private” XML attribute, no adding such internal types to bcp47/collation.xml
Survey tool - suppress naming (coverage)
Rationale/details in email
CLDR `<collation type=”private-kana”>` `<import source=”ja” type=”private-kana”>` ICU `[ja-u-co-private-kana|import]`
Only spec update here.