There's No Such Thing as Plain Text
summary
History shows ASCII is a 1968 7‑bit design with 127 characters and control codes (carriage return, line feed, BEL) that explain CRLF differences; IBM’s code page 437 stuffs graphics into the top half; Unicode solves mixing alphabets but forces choices about composed vs decomposed forms (normalization) and combining diacritics; UTF‑16 fixed‑width storage causes endianness and surrogate issues while UTF-8 encodes ASCII as single bytes; real failures include Chinese text in event logs from a dropped byte and passport/name mismatches.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:56Horizontal Tabs and Line Feeds
- 7:52About Carriage Returns and Line Feeds
- 10:51Case Insensitive Comparison with Ascii
- 20:56Four Different Ways of Normalizing Text in Unicode
- 26:36Utf-8
- 28:35The Vienna Convention on Road Traffic
- 33:07Microsoft Teams
related talks
01h 02mThere's No Such Thing as Plain Text
54mSTRINGS ATTACHED: FROM ASCII TO 🙊🙈🙉
45mI ♥ Unicode
01h 10mInteresting Characters
48mUnicode: Going Down the Rabbit Hole
46mASCII to Unicode, what can possibly go w̵̳̓r̸̡̽ǒ̴̝n̴̬ͣg̶ͤ͜?
56mUnicode - going down the rabbit hole
01h 24mUnicode: From First Principles to Practical Implementation