Characters Names and Keywords (Emoji)

We collect Short Character names and keywords for Emoji characters and sequences. 
 
These are found in Survey Tool under Characters, and they are divided into different category types.
For example, Smileys, People, Animal & Nature, etc...
If you see a "tofu" box in the Code column (as shown in the screenshot below), it may be that your system doesn't have font support to display the emoji images or they are new 69 emoji that will be released in June, 2017.

 
You can use the following reference point if you do not see the images in the Code column:
  1. Go to the page http://unicode.org/emoji/charts/full-emoji-list.html (you might want to leave this window open while you work on the emoji section).
  2. Open the "Find in page" menu (typically control or command-F), and paste in the character you can't see (eg, 😅) or search for the English name (e.g. "star-struck")
  3. You should see the images for the emoji, as below.
 

Short Character Names

In CLDR we provide descriptive but short names for the characters across languages.

 

Goals for the short names collected in CLDR are:

  •  Be unique among emoji names for that language. (You will receive an error in the survey tool if you use
  •  Be short (as much as possible), both written and spoken
  •  Be descriptive of the prevailing color images. The descriptions only have to be enough to distinguish each image; they don't have to have any details beyond that.
  •  Be consistent across images with similar features. (Don’t call 📫 a mailbox and 📬 a post box).
  •  It is not a goal to be immutable; in future versions of CLDR, you can improve names by casing new suggestions if a more appropriate names are available. 
 
When voting on the emoji names and keywords:
  • Follow the middle of sentence rule. See Capitalization guideline.
  • As usual, the names in “en” are American English; where necessary those are customized for “en-GB”. For differences for sub-locale, see Regional Variant guideline.
  • The names in other languages do not have to follow the English name; the descriptions of the colored images may vary by culture. But translators may be informed by the English names.

Character Keywords

Keywords are one or more words or short phrases that can be used to search for the character in your language.
When picking keywords, consider:
  • Unlike the short names, keywords do not have to be unique across different emoji. For example, in English "mailbox" is a keyword associated to any of (📫 📪 📬 📭).
  • Unlike the short names, the keywords do not have to be as short as possible.
  • Each keyword should help narrow down the choices among emoji, so provide as many keywords that are relevant to the emoji.
  • A " | " (pipe) character is used to separate each keyword when there are multiple keywords for an emoji (see screenshot below). When you want to append another keyword, click the + to add, copy the Winning value, and append " | " before adding your new keyword.
  • Like the short names, the keywords should not just be literal translations of the English— the keywords should be base on associations to the image in your language.
  • It does not need to be the same number of keywords in your language as there are in English. 

Unicode emoji names and CLDR short names (Background)

The Unicode Name character property are part of the Unicode standard. They are immutable, unique IDs over all Unicode characters, and limited to uppercase ASCII letters, digits and hyphen. The names often do not apply well to the prevailing practice for emoji images, and are only available in English. Their main purpose is to serve as unique identifiers, and may not be particularly descriptive or short. Example: ɞ  U+025E LATIN SMALL LETTER CLOSED REVERSED OPEN E. Because the Unicode Name is immutable, it cannot change to reflect that.
 
The Unicode Name may inform the English CLDR short names, and that is what we start with (for English) unless one of the other factors come into play. CLDR short names are not limited to ASCII or uppercase, even in English
Comments