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

CLDR Ticket #8400(accepted data)

Opened 2 years ago

Last modified 23 months ago

Plural data for seeds should be under "seed" directory

Reported by: shervin Owned by: mark
Component: plurals Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

ticket:6396

Description

Mark mentioned that if the main data is in "seed", plural data needs be under "seed" as well. I noticed that there are some seed locales with pluralRules under "common/supplemental" (ce, iu, etc.) which needs to be moved to a "supplemental" folder under "seed".

Attachments

Change History

comment:1 Changed 2 years ago by shervin

  • Milestone 28 deleted

comment:2 Changed 2 years ago by shervin

  • Milestone set to UNSCH

comment:3 Changed 2 years ago by emmons

Needs some discussion - many on the TC don't think this will work.

comment:4 Changed 2 years ago by srl

  • Xref set to 6396

more of our tooling would need to be parameterized. CLDRFile itself takes an array of directories ( such as ["common","seed"]. Supplemental data doesn't. See ticket:6396

I think it's a better idea to leave supplemental where it is (covering supplemental data for seed as well). Supplemental data would have very odd merge behavior.

Last edited 2 years ago by srl (previous) (diff)

comment:5 Changed 2 years ago by emmons

  • Owner changed from anybody to mark
  • Phase changed from dsub to rc
  • Priority changed from assess to minor
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 28

comment:6 Changed 2 years ago by mark

  • Phase changed from rc to dsub
  • Milestone changed from 28 to 29

After data submission, the priority for these drops, so moving to the start of the next cycle.

comment:7 Changed 23 months ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.