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

CLDR Ticket #10997(reviewing data)

Opened 4 months ago

Last modified 5 weeks ago

Move Unicode 11 emoji English names from unicode tools to CLDR annotation data for V34

Reported by: pedberg Owned by: mark
Component: annotations Data Locale:
Phase: dsub Review: pedberg
Weeks: Data Xpath:
Xref:

ticket:10995

Description

Move Unicode 11 emoji English names from unicode tools to CLDR annotation data for V34

Attachments

Change History

comment:1 Changed 4 months ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to critical
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 34

comment:2 Changed 3 months ago by mark

generation in GenerateCldrData

  • May need to change org.unicode.cldr.util.Emoji.SPECIALS to have TestAnnotations pass
  • Also add images for visuals
  • Also change the name composition algorithm for components
  • And add documentation of composition of names (for new components like hair styles) to LDML

comment:3 Changed 2 months ago by mark

  • Status changed from accepted to reviewing
  • Review set to pedberg

Still need to do the name composition parts, but can you review the other bits?

comment:4 Changed 2 months ago by mark

  • Status changed from reviewing to reviewfeedback

comment:5 Changed 8 weeks ago by mark

Fix use of collation

comment:6 Changed 8 weeks ago by mark

There is one further change in root.xml, to put bald at the end of the other hair. (This crept in because the hair and skin have special treatment when generation, since they are secondary differences.)

comment:7 Changed 5 weeks ago by mark

  • Status changed from reviewfeedback to reviewing

comment:8 Changed 5 weeks ago by mark

Note most actions for this were for v33.1, but not all. So it was integrated with an SVN copy into v33.1.

View

Add a comment

Modify Ticket

Action
as reviewing
Author


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

 
Note: See TracTickets for help on using tickets.