Cross-platform emoji solution
mwunsch.tumblr.com
mwunsch.tumblr.com
> Do not store emoji unicodes in your database. Store the human-friendly code and support the emoji-cheat-sheet.
I would strongly recommend doing the reverse: store and use standard Unicode throughout your application. If you want support on browsers which do not support Unicode 6 properly, use JavaScript or a web font to substitute the characters in question so you don't need to update every bit if text you've ever stored or displayed when e.g. Chrome lands emoji support in a few releases.
This approach avoids having to fix your proprietary encoding scheme later and also means that less popular user agents automatically get support as soon as they add it.
More to the point, however, you could take the symbols you would have to create either way and package them as a web font - which would only be downloaded on devices without a better choice - or simply make your JavaScript do a simple search and replace on the Unicode character values to substitute the same HTML markup you'd need either way. Again, you could do a client side detection for this to avoid any overhead on browsers with support.
I think I disagree. I'm trying to think of a situation in which a pull request or a campfire chat with emoji has ever made my life better, and I just can't.
If you can't communicate successfully without emoji, then you have a large communication problem that is likely not being solved by their addition.
edit: for clarity.
Chrome has similar problems on Windows. For example, the Mathematical Alphanumeric Symbols work in Firefox, Internet Explorer, and even Notepad, but not in Chrome. http://en.wikipedia.org/wiki/Mathematical_Alphanumeric_Symbo... http://code.google.com/p/chromium/issues/detail?id=109844
if you want to put pictures in your text, just put pictures in your text. html has allowed you to do this since its inception.