veyepar: The Power ⚡️ and Responsibility 😓 of Unicode Adoption ✨

Author(s):	Katie McLaughlin
Location	Room 106
Date	aug Sat 13	Days Raw Files
Start	11:10	First Raw Start	error-in-template
Duration	0:40:00	Offset	None
End	11:50	Last Raw End
Chapters
Total cuts_time	None min.

https://2016.pycon-au.org/schedule/19/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf The_Power_and_Responsibility_of_Unicode_Adoption.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Communication is difficult.

Whether it’s between humans or machines or a combination of the two, trying to translate meaningful information is a lossy process.

Converting languages to use the new Unicode standard is hard, but once it's in place, you get this marvellous feature-add: Emoji compatibility. No longer do we have to make faces with symbols, or be forced to platform-specific emoticons! Rejoice in the extended character set!

Emoji has a rich history as a way to allow the communication of ideas in a reduced amount of data, and dates back to a time where this was important: SMS communications in Japan. However, as social networks feverishly try and clamber into this bandwagon, their implementations of the standard create more issues with miscommunication that aren't already possible with a 12x12 pictograph. 🤔

From the technical to the social aspects, mojibake and UTF-{8,16,32}, this talk will cover why the extended character set provided by the Unicode standard needs to be treated with responsibility by users and platforms alike.

This talk is not just an excuse to see what parts of the conference stack can’t handle Unicode, I promise. 😇

Comment:

production notes