Plain Text
summary
A fast survey of how text encoding actually breaks things: a 5‑wire telegraph to ASCII's 7 bits, 8‑bit code pages, and why Windows stores UTF‑16 leading to Chinese gibberish when a byte drops on the network. Shows concrete bugs (passport name vs ticket mismatch, database collation surprises), explains why UTF-8 is the web win, demos normalization and ligature fonts, and ends with the mnemonic pike matchbox for interoperable plain‑text pitfalls.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:32Intro
- 3:19The Cooking Wheatstone Telegraph System
- 5:48Trinary Encoding
- 6:51International Morse Code
- 10:58Carriage Return
- 16:03Journey with Plain Text
- 17:41Code Page 437
- 20:058-Bit Encoding
- 20:46The Harry Potter Envelope
- 24:26Unicode Consortium
- 30:46Danish Spelling Reform
- 34:40Normalization Forms
- 35:22Inline Strings
- 41:29Utf-8 Encoding
- 43:05Emoji
- 46:09Flags
- 46:23Regional Symbol Indicators
- 46:46The Alphabetical Tags
- 47:32Republic of China
related talks
52mThere's No Such Thing As Plain Text
11mLightning Talk: Encoding - Understanding the Basics
05h 57mEngX Community Day 2
01h 24mUnicode: From First Principles to Practical Implementation
38mTerminal Whispering
25mText files full of punctuation? There must be a better way to code.
17mVisualizing Assertions for Complex Logic Tests
42mThe Command Line A Humble Journey
