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

CLDR Ticket #10230(closed unknown: fixed)

Opened 13 months ago

Last modified 8 months ago

Add Emoji translation guide

Reported by: kristi Owned by: mark
Component: survey Data Locale:
Phase: dsub Review: kristi
Weeks: Data Xpath:


Add information from the Emoji short name proposal(https://docs.google.com/document/d/1eFBPyWdjUqXr2Ti9DYw7oKyXE3QFFO8bPcoNm7RL-xk/edit#heading=h.tpl9ea22nek8) to Translation guide.

Create a new page for Emoji under: http://cldr.unicode.org/translation

Pull out relevant information:

The Unicode names 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.

Thus in CLDR we provide short names for the emoji across languages. Goals for the CLDR short names are:
Be available in each CLDR language
Be unique among emoji names for that language.
Be (as much as possible) short, 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: future versions can improve names.

The Unicode names may inform the English CLDR short names, and that is what we start with unless one of the other factors come into play. CLDR short names are not limited to ASCII or uppercase, even in English. As usual, the names in “en” are American English; where necessary those are customized for “en-GB”. 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.


Change History

comment:1 Changed 13 months ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Component changed from unknown to survey
  • Milestone changed from UNSCH to 32

Add pointer to new page.

comment:2 Changed 12 months ago by mark

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

comment:3 Changed 8 months ago by kristi

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

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

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

Note: See TracTickets for help on using tickets.