emoji-data | readable emoji data built from official Unicode reference | Icon library

Because the numbers are in hex. 0x is a prefix used to indicate hex numbers. Number("261D") is NaN, but Number("0x261D") is 9757.

Other prefixes available in JavaScript are 0b (binary, e.g. 0b11 is 3) and 0o (octal, e.g. 0o11 is 9).

The "1F44D" in this table is the unicode value in hex. Convert this to an integer, that to a UnicodeScalar, and that to a String or Character:

You don't pass a number to the children function, you pass a selector if you want to limit your search to only certain elements. For example, if you wanted only elements, you'd use $("#container").children("span").

Instead of using a for loop, you want to use the each function on the children, and append their content using a callback function:

Not all emoji has Android (Google) PUA code points.

Emoji made in Japanese carrier has had different code points, using private user area (PUA). They are called "Carrier Emoji". Each carriers PUA code points are mapped to Android (Google) PUA code points on Android phones. Thus, in case we show these carrier emoji on Japanese Android phones sold on a carrier's store, we should use Android (Google) PUA code point. After all, these carrier emoji were exported to Unicode 6.0 emoji.

That is why only Uncode 6.0 emoji have their own Google PUA code points and newer Unicode 6.1 (or later) emoji do not.

I have used the following regex pattern successfully before

I was able to get this to work with fontkit by selecting a font from the font collection. I haven't found a case yet where using either of the TTFs included in the "Apple Color Emoji.ttc" gives different results.

NSString is encoded as UTF-16, so U+1F1E6 U+1F1FA can be expressed in code using \u notation: "\uD83C\uDDE6\uD83C\uDDFA". Or, if you use \U notation instead, you can use the actual codepoints as-is: "\U0001F1E6\U0001F1FA".

In Swift, it would be expressed as "\u{1F1E6}\u{1F1FA}" instead.

In either case, you can alternatively just put the Unicode characters directly in the string literal and not escape them at all: "".

Not all emoji glyphs are created from a single Unicode code point. Some characters only have an emoji appearance when combined into an "emoji sequence". This makes it hard to count emoji characters by code points alone. This is what Section 3 in UTR #51 is trying to convey, but it might be improved with some examples:

• U+0031 is 1, but takes on an emoji appearance when combined with U+FE0F U+20E3: 1️⃣ (or a plain appearance with U+FE0E U+20E3: 1︎⃣).
• U+1F170 is , but takes on an emoji appearance when combined with U+FE0F: ️.
• U+2620 is ☠︎, but takes on an emoji appearance when combined with U+FE0F: ☠️.
• (In general, the U+FE0F variation sequence was used to turn many existing characters into a corresponding a emoji sequence without having to encode them as a separate code point.)
• The regional indicator symbols only appear as emoji when they form a country/region code: U+1F1E6 U+1F1F6 , but not U+1F1E6 U+1F1F5 .

The emoji-data.txt file lists all characters that have the Emoji=Yes character property. These are all base characters (e.g. 1, , ☠︎, , , ) that can at least start an emoji sequence, even if they are not a complete sequence by themselves. The emoji-test.txt file lists all complete emoji sequences.