Communication is difficult. Whether between humans, machines, or a combination of the two, trying to translate meaningful information is a lossy process.
Converting programming languages to use the new Unicode standard is hard, but once it’s in place, you get this marvelous feature-add: emoji compatibility. No longer do we have to make faces with symbols or use platform-specific emoticons. Rejoice in the extended character set.
Emoji have a rich history as a way to allow the communication of ideas in a reduced amount of data. They date back to a time where this was important: SMS communications in Japan. However, as social networks feverishly try to clamber onto this bandwagon, their implementations of the standard create issues with miscommunication that aren’t possible with a 12×12 pictograph.
Katie McLaughlin discusses the history of emoji, cross-platform adoption, the Unicode standard, and emoji accessibility in web applications. ✨
Katie McLaughlin has worn many different hats over the years, including a software developer in many languages, a systems administrator for multiple operating systems, and a speaker on many different topics. She’s currently a core developer on the BeeWare project, organizer of KatieConf, and a former board member for Linux Australia. When she’s not changing the world, she enjoys making tapestries, cooking, and seeing just how well various application stacks handle emoji.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com