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

CLDR Ticket #11007(accepted)

Opened 8 months ago

Last modified 4 weeks ago

How to best accomodate working with New emoji for vetters

Reported by: kristi Owned by: backend
Component: emoji Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


New emoji are identifiable in Dashboard under New, but if Dashboard, but working out of Dashboard is unproductive:
Go to DashboardGo to NewClick on one itemWork on that itemGo to dashboardRepeat….

Throwing an idea here since we'll continue to have New emoji come up with every Unicode release:

  1. Add a flag for the new Emoji before they get added in CLDR (e.g. Attribute=New)
  2. Attribute=New get identified by the Survey tool and show in a new category under Characters

Left nav a. Characters

  1. Category
  1. New
  1. Smileys
  1. After resolution, and CLDR modify (?), remove Attribute=New, thus brining in the New set into categorizations that they belong under.


Change History

comment:1 Changed 8 months ago by mark

  • Status changed from new to accepted
  • Component changed from unknown to emoji
  • Priority changed from assess to critical
  • Milestone changed from UNSCH to 34
  • Owner changed from anybody to mark
  • type changed from unknown to tools

Will try:

Change the “artificial” code for Root is distinctive: long, and searchable. NEW_EMOJI_001

comment:2 Changed 8 months ago by mark

Also consider making new emoji be Moderate to start...

comment:3 Changed 7 months ago by emmons

  • Milestone changed from 34 to 33.1

comment:4 Changed 7 months ago by kristi

  • Owner changed from mark to tbishop
  • Milestone changed from 33.1 to 34

This tool change will be for the data in v33.1, but changing this to 34 to exclude from the list of tickets specifically for the v33.1 data changes

comment:5 Changed 7 months ago by mark

The main goal is to have users be able to quickly see which emoji are new, and address those during the first two weeks.

There is a way for them to see all *missing* values in the dashboard, but that doesn't give them context. So ideally it is to give them some way to either filter to just new ones, OR quickly search for in the page.

The simplest way to do that is to just have a different artificial ROOT value. Currently these are of the form Ennnn, like E1234. But the numbering is completely arbitrary, so we can change them around. The proposal in comment 1 is to have something like NEW_EMOJI_001, although on second thought probably better to be:


Just as easy to search for, and is extensible for Emoji 11, etc.

comment:6 Changed 6 months ago by mark

  • Owner changed from tbishop to backend

Short term fix is in separate ticket https://unicode.org/cldr/trac/ticket/10997

Longer term may want to be able to filter by different criteria other than just the coverage level.

comment:7 Changed 6 months ago by mark

  • Priority changed from critical to major

downgrading, since we have reasonable workaround.

comment:8 Changed 4 weeks ago by pedberg

  • Milestone changed from 34 to upcoming

CLDR 34 BRS closing item, move all open 34 → upcoming

comment:9 Changed 3 weeks ago by mark

  • Milestone changed from upcoming to 35-optional

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.