[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #6332(closed enhancement: fixed)

Opened 2 years ago

Last modified 17 months ago

remove or deprecate collations/collation/base

Reported by: markus Owned by: markus
Component: xxx-spec Data Locale:
Phase: Review: emmons
Weeks: 0.1 Data Xpath:
Xref:

Description

The DTD and spec mention a <base> sub-element of <collations>/<collation> which has never been used in any CLDR release, and I believe it is redundant with <import>. Can we remove <base> from the DTD? If not, please deprecate it.

Note: I have had ideas of doing something like <base> that is different from <import>, and possibly more efficient, but have not yet figured out how to make it work reasonably. I would probably not permit arbitrary bases. (Only special ones like search/eor/unihan, and prebuild them.)

DTD:

<!ELEMENT collation (alias | (base?, import*, settings?, suppress_contractions?, optimize?, (cr* | rules?), special*)) >

<!ELEMENT base (alias|special) >

Spec:

The optional base element <base>...</base>, contains an alias element that points to another data source that defines a base collation. If present, it indicates that the settings and rules in the collation are modifications applied on top of the respective elements in the base collation. That is, any successive settings, where present, override what is in the base as described in Setting Options. Any successive rules are concatenated to the end of the rules in the base. The results of multiple rules applying to the same characters is covered in Orderings.

Attachments

Change History

comment:1 Changed 2 years ago by emmons

  • Owner changed from anybody to markus
  • Priority changed from assess to medium
  • Type changed from defect to enhancement
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 24final

comment:2 Changed 2 years ago by markus

  • Status changed from assigned to accepted
  • Review set to emmons

John replied:

I think the agreement was that you could indeed REMOVE it.

comment:3 Changed 2 years ago by emmons

  • Review emmons deleted
  • Milestone changed from 24final to 24rc

Mark brought this as an issue to the TC, that the element should have been deprecated instead of removed, in order to maintain compatibility of DTDs whenever possible. Please put the element back in the DTD and mark it as deprecated. I apologize for the confusion. Many of us on the TC thought that we had indeed agreed to remove it when we initially discussed it.

comment:4 Changed 2 years ago by markus

  • Cc emmons added
  • Review set to emmons

r9233: restore the collations/collation/base element but deprecate it

comment:5 Changed 2 years ago by emmons

  • Status changed from accepted to closed
  • Resolution set to fixed

comment:6 Changed 17 months ago by emmons

  • Milestone 24rc deleted

Milestone 24rc deleted

View

Add a comment

Modify Ticket

Action
as closed
The ticket will be disowned. The resolution will be deleted. Next status will be 'new'
Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.